Problems on admin side

Hi Salvatore,

since I activated the “stripe cookies” option on your plugin, it was working fine for a bit and now, we’re stuck outside of admin and unable to connect at all.

I’m having this error on my side : Error: Cookies are blocked or not recognized by your browser. You must enable cookies to use WordPress.

I tried to deactivate your plugin, purge the CF cache, but nothing is working. Can you please me to found a solution, as I guess it’s related?

Thanks,
Sylvain

A quick follow up from my problem. If you remember, you told me to activate the option “Strip response cookies on pages that should be cached” on your plugin because I noticed sometimes my home page was having “cf-cache-status : BYPASS”. So I activate your option (not knowing what it will do!) but one day after that, I was unable to connect to my admin. I had to deactivate your plugin through FTP first. Luckily, I was still connected to my admin from yesterday and I had to activate again and set the option “strip cookies” on OFF to be able to connect again in incognito mode or from another browser. So, there’s something wrong here with this option in my humble opinion.

For now, there’s still something wrong as I have an error every time I hit “test cache ” ->>

Cache status: DYNAMIC – Something wrong in your Cloudflare setup. Please check that the page rule was created correctly and that Cloudflare is respecting the original HTTP response headers.

I checked my homepage on GTmetrix but I’m having this : cf-cache-status : DYNAMIC…so something is wrong too.

Can you please have a look more closely and help me to figure this out? If I don’t activate the “stripe response cookies” option, I’m having sometimes (why?) cf-cache-status : BYPASS so that’s not good and if I activate it, I’m stuck outside my admin and can’t log in to my website anymore.

Thanks,
Sylvain

A quick update on my issue here.

I don’t know why and how but the cache-status is now back to normal. But again this afternoon I add trouble with cache-status = BYPASS on my home page. Sometimes it’s on BYPASS and 30′ later it’s on HIT. I can’t understand why. I tried to compare waterfall from GT Metric between a normal report with HIT and one with BYPASS here: https://gtmetrix.com/compare/XnQsrhYK/ySJ0bJcK

I’m not good enough to understand what’s happening here, but I do see those differences :
– Every time cache status is HIT I have a first line “age: xxx”
– I only have one set-cookies when it’s working fine instead of two set-cookie when the cache status is on bypass. There seems to be a conflict here, especially on the date of “expiration”
– Every time the cache status is BYPASS, my result is far worse (slower)

Can you help me to figure out where this problem is coming from?

Thanks,
Sylvain

Hi again,

I have any idea why but it seems that the cache is bypassed because of a language cookie (you can see on the pll_language=fr), and it seems to be related to the plugin Polylang I use.

So I guess there is somehow a conflict between your plugin and Polylang and the way it handled it. Any help would be much appreciated ??

Thanks,
Sylvain

Hi @lesdeuxpiedsdehors ,
sorry for late response. Your problem is Litespeed.

On Litespeed is not possibile to use the option “Overwrite the cache-control header for WordPress’s pages using web server rules”.

This option basically tells the web server to overwrite the Cache-Control header when WP Cloudflare Super Page Cache, through its own custom response header, considers it appropriate that the page should be inserted in the Cloudflare cache. That is, when the x-wp-cf-super-cache-active response header is equal to 1.

This option is indispensable when other plugins create their own cache-control headers which could interfere with Cloudflare’s cache.

To do this, on Apache just insert the following condition at the end of the Header rule, as per official documentation of the mod_headers module:

“expr=resp(‘x-wp-cf-super-cache-active’) == ‘1’”

But Litespeed does not support “expr=value” (response of today):

https://www.litespeedtech.com/support/forum/threads/litespeed-ignores-expr-in-htaccess-mod_headers.18620/

So it’s not possibile on Litespeed create/edit response HTTP headers based on the value or existence of others response headers.

But the main problem is that Litespeed, while ignoring expr = value, still creates the Cache-Control header, thus allowing Cloudflare to cache also pages that should not be cached (like those of the backend).

So in a nutshell, if you need to activate this option to run this plugin on your Litespeed server, unfortunately it is not currently possible for you to use it.

I want to clarify that this is not a limitation of this plugin.

But I have good news for you. I am working on an option that uses Cloudflare workers to manipulate cache behavior. The only drawback is that workers are only free of charge up to 100,000 requests per day.

Hi @salvatorefresta,

Thanks for your answer. I guess it’s too difficult for me to understand here even of I do understand the problem might be related to Lite Speed.

I’m not sure, we understood each other. I don’t use in my set-up the option “Overwrite the cache-control header for WordPress’s pages using web server rules”. Everything seems to be working fine for now, but sometimes, I just don’t understand why my cache-status is bypass instead of hit? Is this related to what you said? Or is t something else at all?

And what about the problem I was stucked outside my admin after activating the option“Strip response cookies on pages that should be cached” on your plugin ?

Thanks ??
Sylvain

Hi @lesdeuxpiedsdehors ,
cookies should be stripped out only on cached pages (not for backend, ajax and login pages). Please open your .htaccess file and remove these lines:

Header unset Set-Cookie “expr=resp(‘x-wp-cf-super-cache-active’) == ‘1’”
Header always unset Set-Cookie “expr=resp(‘x-wp-cf-super-cache-active’) == ‘1’”

Again here, Litespeed ignores expr expression and strips out cookies on all pages.

Please try, purge the cache and let me know if it works. Remember that if you save the settings, these lines will be added again on your .htaccess file and you need to remove them.

In the next release I will avoid that it will be done in case of Litespeed web server

HI @salvatorefresta

thanks for your answer. Sadly you lost me here ??

I don’t understand what you’re trying to solve here? The only problem I’m sometimes having is that by cache status is sometimes “bypass”. most of the time, it’s hit and everything works fine. I just can’t use the “Strip cookies option” otherwise, I’m stuck outside my admin panel.

Are we still talking about this problem ?

Hi @lesdeuxpiedsdehors ,
Yes I’m talking about the cookie problem.

If you have sometime a bypass may depends from dynamic cookies like in the picture. It’s a Cloudflare behavior (as other common cache systems)

Hi again @salvatorefresta

Do you think if I remove this from my .htaccess, it might solve my problem of Strype cookies but it won’t work as I use Lite Speed? Is that it?

Header unset Set-Cookie “expr=resp(‘x-wp-cf-super-cache-active’) == ‘1’”
Header always unset Set-Cookie “expr=resp(‘x-wp-cf-super-cache-active’) == ‘1’”

About having sometimes bypass cache status, don’t you think it would be related to a language cookie ( “pll_language=fr”) from Polylang plugin ?

Yes but if you try to update to version 4.1.3 and try to re-save the settings, these lines should be automatically deleted from your htaccess because this version recognizes if you are using Litespeed.

Let me know

Ok, I will then wait for the version 4.1.3 and test it. This way I will be able to use the “Strip response cookies on pages that should be cached” on “ON”.

Because at first, you told me the problem with having “bypass” cache status can be solved with this option ON. When I tried it, I was stuck and couldn’t log in anymore.