different setting of mag age?

No it is not working properly. As when the plugin will work properly you will see that the value of cache-control header is same as the the x-wp-cf-super-cache-cache-control header.

Currently it seems the cache-control data is being set either by some server rule or some plugin/must use plugins. Find out what’s adding that and remove it so that the plugin can manage your cache-control header.

I would like also to ask, if google bots see cached or uncached pages?

– If the Google bot is accessing from a location where the page is already cached in the CF datacenter then they will get cached version as bots are treated like any other non-loggedin user.

I enabled this option:
Overwrite the cache-control header for WordPress’s pages using web server rules

but I get the same response.

Now, except from the different setting for max-age of cache, the plugin works properly ?

As I said you need to figure out what is adding the current cache-control header. If it is a server rule you need to remove that.
For overwrite cache control header – are you using an apache or lightspeed server?
Also check if there are other plugin which might be adding that cache control rule.

Now, except from the different setting for max-age of cache, the plugin works properly ?

– Until the plugin is handle;ling your cache control header it won’t be able to do it’s work.

The only plugin that look relevant is redis, but I don’t think that its possible to have conflict with redis and yours.

I contacted with hosting provider and told me that there is no setting about cache in server.

Is there any possibility to there is any problem with cloudflare settings?

I attach also the .htcaccess file:

https://justpaste.it/9sbku

I notice that except the value of cf-cache-status is HIT, when I make changes age price is refreshed and recent.

These are the respond header:

View post on imgur.com

I am sorry if I insist, it’s sure that plugin doesn’t work, if max-age is different?

It’s not about maxage. You are totally missing the point. If you look at the value of x-wp-cf-super-cache-cache-control you will see that there is not just maxage but also s-maxage there. Maxage is just for browser caching whereas s-maxage is for talking to CLoudflare datacenter cache maxage.

Also if the plugin is unable to modify the cache-control header of your sites then it won’t be able to automatically bypass the cache for loggedin users and things like that.

So, as I said before the question you need to ask are:
1. Why the cache-control value is not same as x-wp-cf-super-cache-cache-control
2. Which code is currently adding the current maxage value?
3. Remove that code and check after that if the plugin is able to modify the cache-control data on it’s own
4. If you also have other cache related plugin, try disabling that and see if that work.
5. Check your must use plugins and make sure there is no unrecognized thing that might be causing it

• This reply was modified 3 years, 7 months ago by iSaumya.

Oh! I am noob and I confused maxage with s-maxage.

In firefox I see these headers:
https://pastebin.pl/view/ca02b060

In cmd with curl I see these headers:
https://pastebin.pl/view/0c8f7016

I wondering why I see x-wp-cf-super-cache headers only on cmd (not in Firefox) and if it’s ok to have the value miss to X-Cache.

Could you please tell me if these headers are correct?

Sorry for keeping asking, I am trying to figure out.

• This reply was modified 3 years, 7 months ago by georgew21.

On the curl screenshot, I can see that the cache-control is showing the right data.
Also when I checked the site link you have shared I see the plugin is working properly and the value of cache-control matches the value of x-wp-cf-super-cache-cache-control.

Screenshot:

View post on imgur.com

View post on imgur.com

So, right now as I can see the plugin is working properly on your website.

Even on firefox I see now issues: https://i.imgur.com/NmwSool.png

ok thanks a lot ! You are awesome.

As fas as that using curl -i , I see as “x-cache: MISS” is ok? Shouldn’t be HIT this too?

https://pastebin.pl/view/0c8f7016

Hi,
x-cache is not related to this plugin. CF-Cache-Status is what comes from Cloudflare. It is either coming from some other caching plugin you are using in your site, which I will highly recommend removing.

Or they are coming from some server-level cache you have, which again I will suggest turning off if you can.

• This reply was modified 3 years, 7 months ago by iSaumya.

Ok! thanks again!