Plugin Contributor
iSaumya
(@isaumya)
Hi,
you don’t need to add the Edge Cache TTL. Can you please remove that and let me know so that I can test your site and see what’s going on? Causing looking at the site header it seems even if you remove that Edge Cache TTL directive, your pages should still be properly cached.
After turning off the Edge Cache TTL, I cleared the cache and gave out a statute of bypass, then miss but after several page reloads it gave out a hit.
on other pages, the statuses also alternate in the same order when the page is refreshed
Plugin Contributor
iSaumya
(@isaumya)
But I am still seeing HIT:
View post on imgur.com
Oh! Ok Wait. Now I’m seeing BYPASS:
View post on imgur.com
This is interesting. It seems Cloudflare is not respecting the cache-control header.
1. Do you have any other page rule that is modifying the cache behaviour in any way?
2. Do you have any worker that is modifying the cache behaviour?
3. Inside the cloudflare settings can you double check that the browser cache ttl is et to respect header?
1. no http://prntscr.com/iK0l36ODs9f7
2.no.I disabled all caching and optimization plugins except yours.
Cloudflare also did not include workers
http://prntscr.com/ZRP9jxkD1lFz
3.http://prntscr.com/ZjC7kCMz0K1V
Plugin Contributor
iSaumya
(@isaumya)
Huh! Now that’s wired, cause the plugin is adding the cache-control header properly but Cloudflare not respecting them: https://i.imgur.com/mLhv5w6.jpeg
Oh wait, I found the issue. It’s because cookies are being set to those pages: https://i.imgur.com/rVWKpx8.jpeg
Anytime, custom cookies gets added to a page and there is a set-cookie in the response header, Cloudflare will not cache the page thinking the cookie value might be used inside the page to show dynamic content. So, you need to figure out what plugin is adding that cookie and make sure that cookie doesn’t get added.
That will solve your issue.
Thank you for your hard work.
Can you please tell me how to determine which plugin these cookies may belong to?
Plugin Contributor
iSaumya
(@isaumya)
Hard to say. The cookie name is wschid. Chekc the plugins you have and if any one of them has a short name like that. Or you can ask you r host to run a search on the server to see exactly on which file that string is present to see from where it is coming from.
I was told that it turns out that your plugin gives this cookie
http://prntscr.com/co3HIZpDjMf1
Plugin Contributor
iSaumya
(@isaumya)
LOL! That’s clearly wrong information provided by your host. You can download the plugin code and search for wschid inside the plugin code. You will find no presence of it.
Also your host ran a total useless search inside the .log files for wschid – which would never provide any useful data.
Also them to run a search inside the /public/ or /public_html/ folder (whichever is your root site folder). Ask them to search for any file that has wschid mentioned inside the content.
The command for that should look something like this:
grep -rli wschid --include='*php'
P.S.: I can’t believe that I have to share a UNIX command for something that the host should have known/run themselves.
We greatly appreciate the comments of our foreign colleagues.
Also, many thanks for the extremely valuable science of UNIX teams.
However, we can assure you that the only place where these cookies are mentioned is in the file
./wp-content/wp-cloudflare-super-page-cache/mamaclub.info/debug.log
From which a conclusion was drawn regarding the involvement of the wp-cloudflare-super-page-cache plugin.
Also, as you know, cloudflare is a third-party service that has cache management capabilities.
So, it is likely that these cookies are generated there.
——————————
Regards,
Oleksandr K.
Technical Support Team
Can activate the function in the plugin: Delete cookies in responses on pages that should be cached?
Plugin Contributor
iSaumya
(@isaumya)
Hi,
That is truly a wired answer cause if that cookie is mentioned in the debug.log which is actually not a source file, that must needs to be mentioned on some actual source code in the server. I can assure you that this plugin does not add any cookies what soever, but if you want, feel free to read the source doe. It’s fully open source.
Can activate the function in the plugin: Delete cookies in responses on pages that should be cached?
– yes but use that will very high caution as it will remove all cookies, so, if you have any other plugin that adds any actual cookie that the site actually uses, it will remove that too. So, when using that option, it is HIGHLY recommended to test all possible permutations and combinations of your website to see if any of your webpages are behaving the way they are not supposed to.
What I need to do I do not understand?))
if you do not turn off cookies in the settings, and the hosting did not find these cookies except for your plugin
Plugin Contributor
iSaumya
(@isaumya)
If you enable the stripe response cookies option inside the plugin settings then you need to test your site thoroughly in an incognito window as a normal viewer to ensure every part of your website is working as it is supposed to.
Cause that option will remove all cookies from the response header. So, if you actually have any plugins, that use come cookies to do something, it might cause issues there. Hense the testing.
I understood it)
What else can you do without this option?
Plugin Contributor
iSaumya
(@isaumya)
If you don’t want to use this option. Then the only way is to figure out what plugin/external script is adding that cookie. You can try disabling all the plugins you have on your site and check if the cookie is still there. Then try the default theme and so on. You know the drill. Basically you need to figure out what is adding that cookie and remove that.
