Law

Thank you @isaumya
Finally I’ll quit CloudFlare. So I won’t follow up the defect.
Thanks

Hello @isaumya

Thank you for your reply.

I’ve tried that (exclude “wc-api”) but with a slightly different format of the URL. I’ll try with yours.

I thought about the user’ip that looks to be in cause :
Does WP Cloudflare Super Page Cache manage the replacement of CF’s IP the user’s one ?
Methods are explained here : https://support.cloudflare.com/hc/en-us/sections/200805497-Restoring-Visitor-IPs

Regards,
Law

Complement : If I deactivate the main WAF in Cloudflare, there’s still the problem.

Perfect, thank you

Last thing please @isaumya

P.S.: Setting cache for 1 week will still give Google messages as that is too short of time for cache. The default time set by this plugin is always the best choice as the default has been set keeping a lot of things into consideration.

I’ve erased default value so what were these values for Cloudflare Cache-Control max-age and Browser Cache-Control max-age ?
When you say 1 week (604 800) is too short, which of the 2 values are you talking about ?

Thanks,
Regards,
Law

Hi @isaumya

Yes, the screenshots are from the plugin I use.
But this plugin does modify the .htaccess file. It just allow to do it from a simpler interface.
Having no coding competence, I’ll keep on like that.

Thanks again for your help,
Regards,
Law

Hi @isaumya

Thanks for your very complete and clear answer. Finally I’ll cache more pages so I’ll let Cloudflare Cache-Control max-age last 1 week. And your Google Page Speed argument convinced me.

As you evoque the need of HTTP Headers, I’d just need to know – but without going further in the details -, according to you and you great experience of Cloudflare, if these 6 elements in the HTTP Headers are really useful… Or if I can removed all 6 since I use Cloudflare (so it already takes them into account).
I attached them here :
– Security (5) : https://imgur.com/a/HgV2Ds1
– Compression (1) : https://imgur.com/a/GLGB7Hb

Thanks a lot,
Regards,
Law

Ah ok.

OK, so its should be uncached with Miss. Unfortunately the behaviour is different. I really don’t see the cause of the problem. I’ll investigate later.

For now I’ll use the URL exclusion as a solution.

Thank you

Hum… no

Please refer the previous answer :

For a logged in user :

1/ First display of the page : x-wp-cf-super-cache-worker-status: miss => No more uncached = KO

2/ Second display after manual refresh : x-wp-cf-super-cache-worker-status: bypass => uncached = OK

The solution would to have the first display with x-wp-cf-super-cache-worker-status: bypass => A user must see the page as logged in directly.

Do you see what I mean ?

Regards,

yesOk,

Please find here the response of the 2nd page after a refresh :

HTTP/2 200 OK
date: Sun, 30 Aug 2020 16:47:56 GMT
content-type: text/html; charset=UTF-8
cf-ray: 5caffefe0e306924-CDG
cache-control: no-store, no-cache, must-revalidate, max-age=0
expires: Sun, 30 Aug 2020 16:47:53 GMT
link: <https://mysite.com/wp-json/>; rel="https://api.w.org/", <https://mysite.com/>; rel=shortlink
set-cookie: _RUgxGTXBH=1EzR%5D9hTqD; expires=Mon, 31-Aug-2020 16:47:50 GMT; Max-Age=86400; path=/; secure
vary: Accept-Encoding
cf-cache-status: DYNAMIC
cf-request-id: 04e1ddb2c9000069244aba0200000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
pragma: no-cache
set-cookie: BOTtd_WwiplY=zSZDa1F0bYpI; expires=Mon, 31-Aug-2020 16:47:50 GMT; Max-Age=86400; path=/; secure
set-cookie: ADYViFQfxhcR=CdpT2lFc8%5Bsg; expires=Mon, 31-Aug-2020 16:47:50 GMT; Max-Age=86400; path=/; secure
set-cookie: cerber_groove=66cd5c00051b54fcf6b3d9838896e29f; expires=Mon, 14-Sep-2020 16:47:51 GMT; Max-Age=1296001; path=/; secure
set-cookie: cerber_groove_x_8CvHETjXQ3R4mDPSOsJ91KVpFdbgL0q=lvxXFEiQ0Wpf56M7n9sBhmaL4rq32Kke; expires=Mon, 14-Sep-2020 16:47:51 GMT; Max-Age=1296001; path=/; secure
set-cookie: asgarosforum_unique_id=deleted; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/
x-wp-cf-super-cache: no-cache
x-wp-cf-super-cache-cache-control: no-store, no-cache, must-revalidate, max-age=0
x-wp-cf-super-cache-worker-status: bypass
server: cloudflare
content-encoding: br
X-Firefox-Spdy: h2

I don’t see “HIT” but the x-wp-cf-super-cache-worker-status: bypass seems OK.

But… how to correct that problem ? A logged in user needs to see directly (without any refresh) the page without cache.

Thank you,

–

Sorry I did not see your last sentence. Ok, I can make an exception on this page / URL but that’s annoying as it is the homepage. I’d want to let a cache on it (even short). Would you see another solution ?

Regards,

Hi @isaumya

Ok, so :

After a successful login on the login page on my site, there’s another welcome page, where the response header of the 1st request is :

cache-control: no-cache, must-revalidate, max-age=0
cf-cache-status: DYNAMIC
cf-ray: 5cafbfa74f4fee6d-CDG
cf-request-id: 04e1b61c8b0000ee6d5490b200000001
content-type: text/html; charset=UTF-8
date: Sun, 30 Aug 2020 16:04:40 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Wed, 11 Jan 1984 05:00:00 GMT
location: https://mysite.com/welcome-page/
server: cloudflare
set-cookie: _RUgxGTXBH=1EzR%5D9hTqD; expires=Mon, 31-Aug-2020 16:04:37 GMT; Max-Age=86400; path=/; secure
set-cookie: BOTtd_WwiplY=zSZDa1F0bYpI; expires=Mon, 31-Aug-2020 16:04:37 GMT; Max-Age=86400; path=/; secure
set-cookie: ADYViFQfxhcR=CdpT2lFc8%5Bsg; expires=Mon, 31-Aug-2020 16:04:37 GMT; Max-Age=86400; path=/; secure
set-cookie: wordpress_test_cookie=WP%20Cookie%20check; path=/; secure
set-cookie: cerber_groove=66cd5c00051b54fcf6b3d9838896e29f; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; secure
set-cookie: cerber_groove_x_8CvHETjXQ3R4mDPSOsJ91KVpFdbgL0q=lvxXFEiQ0Wpf56M7n9sBhmaL4rq32Kke; expires=Thu, 01-Jan-1970 00:00:01 GMT; Max-Age=0; path=/; secure
set-cookie: wordpress_sec_4801951b03b5049ffc3ffadb66d181d2=user1%7C1598976278%7Cvtf0bHrW1xKrlqiKEHzBCEKXyVK7uOCHx6P1cbZjkzt%7Cd5154f95eab204bd1cb00adf34f6c612af91f4d32fe73fea617f9b4069ae4c69; path=/wp-content/plugins; secure; HttpOnly
set-cookie: wordpress_sec_4801951b03b5049ffc3ffadb66d181d2=user1%7C1598976278%7Cvtf0bHrW1xKrlqiKEHzBCEKXyVK7uOCHx6P1cbZjkzt%7Cd5154f95eab204bd1cb00adf34f6c612af91f4d32fe73fea617f9b4069ae4c69; path=/wp-admin; secure; HttpOnly
set-cookie: wordpress_logged_in_4801951b03b5049ffc3ffadb66d181d2=user1%7C1598976278%7Cvtf0bHrW1xKrlqiKEHzBCEKXyVK7uOCHx6P1cbZjkzt%7Ce3f68e17c4e3757806a704115add54811c6ff7271e0f0e7f4f556008d6c27a21; path=/; secure; HttpOnly
status: 302
vary: Accept-Encoding
x-frame-options: SAMEORIGIN
x-redirect-by: WordPress
x-wp-cf-super-cache-worker-status: bypass

–

Then, on this welcome page I click on a validation button and arrive on 2nd page. Here, the response :

cache-control: s-max-age=604800, s-maxage=604800, max-age=300
cf-cache-status: DYNAMIC
cf-ray: 5cafbe64bbeaee6d-CDG
cf-request-id: 04e1b552f00000ee6d548b6200000001
content-encoding: br
content-type: text/html; charset=UTF-8
date: Sun, 30 Aug 2020 16:03:49 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Sat, 28 Nov 2020 16:03:44 GMT
link: <https://mysite.com/wp-json/>; rel="https://api.w.org/", <https://mysite.com/>; rel=shortlink
server: cloudflare
status: 200
vary: Accept-Encoding
x-wp-cf-super-cache: cache
x-wp-cf-super-cache-active: 1
x-wp-cf-super-cache-cache-control: s-max-age=604800, s-maxage=604800, max-age=300
x-wp-cf-super-cache-worker-status: miss

=> On this second page, it is as if the user was logged out.

Hi @isaumya

Thanks finally I’m done with it, I found how to set up.

Regards,
Law

Thank you @isaumya for these elements. Glad to know there’s nothing more to change on the CF dashboard.

Now, with the current configuration in WPCSPC, my site is not broken anymore, but a logged in user still has cache (the pages he sees could’nt be cached).

Current settings : The Worker mode is activated, but I disabled all the other options in “Cache” and “Advanced” tabs.

Could you see what setting is missing to get the cache for the logged in users ?

Thank you,
Law

Hi @isaumya

So, let’s tell that I cannot not use the Page Rule mode. Because once activated, it breaks my site (chat module unusable).

Now, I’m focus on Worker mode. In complement on what I detailed in my previous message (“swcfpc_worker” mentionned in Cloudflare > Workers, no variable activated…), what is missing to make the worker work ?

I’m not looking to overwrite anything.
I just need you to show me the remaining steps in order to make the worker fully functional.

Thank you for your help,
Regards,
Law