bandsaw12

@mhdizmni Updated this morning and the counts are working again. Fantastic.

Thank you for the quick response to my issue. Keep up the good work on this plug-in.

Jeffrey

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.

Thank you. The X-Varnish is the piece of information that is missing in your documentation. If I may suggest, add to your product description exactly what header names your product is looking for. As I read the description, I am assuming the plug in works for both NGINX and Varnish. I don’t read it as NGINX with Varnish.

Just curious, do you really need the age header at all? If you get a cache status of HIT, then the page is cached? Yes?

I will try changing my cache status header to X-Varnish and see if I get this working.

Also, again, if I may so, if negative results of the cache checks does not always impede the operation of your plug in, the failed check should say so. As it is, the Age check shows red and I take it as meaning a show stopper.