Hi @laugau,
You are facing problem because of improper cache-control
header value set that nginx.conf
level.
I would recommend you to do the following:
1. Inside the nginx.conf
file remove/comment out the rules related to adding cache-control
or expires headers to files/requests.
2. Inside the plugin settings, under Cache tab, scroll down to the bottom and enable Add browser caching rules for static assets
and click on Update Settings
3. Then click on the this page
like to view the nginx
rules generated by the plugin and which you need to add in your main nginx.conf
file. (Screenshot: https://i.imgur.com/nXohsGa.png)
After this check the response header of your webpage and check if the value in the cache-control
header matches to the value in x-wp-cf-super-cache-cache-control
header.
If you are still having issues, then you can also enable the Overwrite the cache-control header for WordPress's pages using web server rules
option under that cache tab of plugin settings and it will generate another line of nginx config which you need to add in your nginx.conf
file.
Please note that each time you update your nginx.conf
file make sure you restart nginx.
I find it not super clear if we have to keep the Page Rules or not…
– First delete any page rules you have that you might have added before using this plugin. Then once you enable this plugin it will add 1 cache everything page rule to your CF account. Do not delete it or tinker with it in any way. That’s the only page rule you need for handling all page caching.
You can have other page rules related to forwarding and other things but never have a page rule that may be modifying cache behaviour in any way as it is always managed by this plugin.