no-store, no-cache, must-revalidate, max-age=0

  • Resolved grahamsg

    (@grahamsg)


    11 months ago

    After activating the plugin, the following error message was relayed –

    “Page caching seems not working for both dynamic and static pages.

    Error on dynamic page (https://www.lip-sunglasses.com): Cache status: BYPASS – Cloudflare has been instructed to not cache this asset. It has been served directly from the origin.

    Error on static resource (https://www.lip-sunglasses.com/wp-content/plugins/wp-cloudflare-page-cache/assets/testcache.html): Unable to find the Cache-Control response header.”

    All plugins were then deactivated except for Super Page Cache for Cloudflare. However Cache Status is still BYPASS. I contacted our host and their response is as follows:

    “We have investigated your case and I would like to inform you that the server where your websites are hosted has NGINX which is a caching mechanism. Because of that, the first thing I tried to do was to clear the server-side cache and check for any custom rules.

    The cache did not work. After that, I tried to deactivate all the rules inside the .htaccess file for your website in case they were causing conflict, however, the cache plugin still did not detect the cache. Finally, to rule out our server-side caching (NGINX), I have deactivated the same on the server and tested the page with the cache one more time – unfortunately, it did not make any difference.

    I also found an old cache/ folder on the website which I have renamed (in order to deactivate it) but again, the plugin cache was not detected. Since I have tried every possible option from our end, I think the problem is related to the plugin itself since there is no trace of problems on the server.

    So I will suggest you check them and if needed, reach the developers of the plugin as the same appears to be not functioning properly.

    Of course, if any actions are needed on the server form our end, let us know.”

    I would be most grateful if you can take a look at what is happening, and why caching is being bypassed on our site.

    Thanks in advance you for any help you can offer.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    Looking at the cache-control header of your website, it seems that the value is being set by something else (some plugin or server rule). As the value of cache-control and X-Wp-Cf-Super-Cache-Cache-Control should match when the plugin is working properly. Which is not the case for your site.

    So, you need to figure out from where the private, proxy-revalidate, s-maxage=0 cache-control header is getting added and remove that.

    Screenshot: https://i.imgur.com/UVbNphZ.jpeg

    Thread Starter grahamsg

    (@grahamsg)

    Hi

    Thanks for your reply.

    I forwarded your comment to our server support team. It appears there’s a conflict of your plugin with my server’s use of “Engintron” (which apparently integrates nginx on cPanel servers). Here’s their reply…

    Hello,

    Thank you for your patience so far.

    After investigating the matter a bit, I noticed an option in the plugin’s settings called:

    Overwrite the cache-control header for WordPress’s pages using web server rules

    After enabling that setting, it added rules into your .htaccess file which does appear to have fixed the issue.

    However, after monitoring for a bit, I noticed that the Engintron service on your server was actually causing a disturbance with the way the cache plugin worked and unfortunately, I was unable to find the documentation for the plugin to see if there are any possible fixes, so, I had to disable Engintron.

    Considering the information above, if you wish to use Engintron, you can consult with the plugin developers for more details on how to adjust the server-level configuration for Engintron as it differs from the one for Nginx and we will happily assist you with that.

    Thank you for your assistance

    Plugin Contributor iSaumya

    (@isaumya)

    Hi,
    I don’t see exactly how the issue is caused cause the only thing that this plugin handle is the Cache-Control header.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘no-store, no-cache, must-revalidate, max-age=0’ is closed to new replies.