Cached page are served to logged-in users

please provide the report number

you can get it in toolbox -> report -> click “send to LiteSpeed”

report number VKRJECVS
now i had to disable cache, but we also have a staging website so let me know if you need access to it for testing. We also have Cloudflare active.. not sure if it can cause conflicts.

Thanks for your help!

then please do me a report from stage site

Ok, so report on stage is JTHWVSQV
Actually it seems to be working on stage, but not on production. Only difference I can think of if that on prod we ave cloudflare active. Please let me know if there is some specific setting for this.

could you please check on both sites , the http response header when you visit it as login user ?

Both response headers are
no-cache, must-revalidate, max-age=0
Indeed it seems to be working now.. probably it was some caching issue on the cloudflare side.
I’ll let you know I encounter any other issue

hmmm? no , I was referring to x-litespeed-cache or x-litespeed-cache-control header.

Headers are
X-Litespeed-Cache: hit
both on production and staging, but on production it shows me the wrong page content when logged in.
I just want to disable cache for logged-in users!

send another report number from PRODUCTION with cache enabled MXKAJNPP

Looking at the log, the difference between Production and Staging
is:
– Staging
[*****29:64580 2 1WP] [Router] get_role: subscriber

– Production:
[*****29:10058 2 K4y] [Router] get_role:
[*****29:10058 2 K4y] [Vary] role id: failed, guest

Do you have any idea on why the user role / logged in is not recognised on prod?