Conversation
review · 2 starsSpent most of the day working on getting this working with a remote NGINX reverse proxy. The plug-in keeps complaining about no age header in the response. Google seems to suggest that etags and age headers no longer supported in dynamic content with NGINX. Plug-in help is of no help on what header the plug in is expecting to see in order to work. removed. Will have to keep deleting the cache the old manual way. This topic was modified 2 years, 8 months ago by bandsaw12 .
It’s a little unfair to post about this as a support question and a bad review in the next day, @bandsaw12 https://wordpress.org/support/topic/age-header-missing/ And the error is correct. Nginx dropping support for age headers is something that happened, but it’s still an HTTP standard. The fact that Nginx is being weird doesn’t invalidate the check. That said, the plugin will still work . The checker doesn’t work correctly for your site, but the cache-flush is not reliant on that.
After trying to figure out what headers the plugin wanted to see for about 5 hours without any documentation as to what you were expecting to see from the NGINX headers, I see the this as appropriate. I will concede maybe it should have had two stars, but then again, I never got it working. Documentation says it works with Varnish and NGINX – not the combination of both required (just that the PURGE request has to be honored). It would not be normal for NGINX to respond with Varnish is it’s header. Improve the documentation to tell users ‘exactly” what your plug in is looking for in the headers for proper operation and I will give this another go.
It’s a little unfair to post about this as a support question and a bad review in the next day, @bandsaw12 https://wordpress.org/support/topic/age-header-missing/ And the error is correct. Nginx dropping support for age headers is something that happened, but it’s still an HTTP standard. The fact that Nginx is being weird doesn’t invalidate the check. That said, the plugin will still work . The checker doesn’t work correctly for your site, but the cache-flush is not reliant on that.
After trying to figure out what headers the plugin wanted to see for about 5 hours without any documentation as to what you were expecting to see from the NGINX headers, I see the this as appropriate. I will concede maybe it should have had two stars, but then again, I never got it working. Documentation says it works with Varnish and NGINX – not the combination of both required (just that the PURGE request has to be honored). It would not be normal for NGINX to respond with Varnish is it’s header. Improve the documentation to tell users ‘exactly” what your plug in is looking for in the headers for proper operation and I will give this another go.