serving old cache with LSCWP_CTRL before_optm

I have guest mode enabled and that’s probably when it started. However today’s case is more about serve stale. After disabling serve stale I can see the changes. With enabled serve stale despite clearing all cache/ucss etc. it’s still gonna show stale version until when exactly?

I visit page, it’s cached now. Cache is purged, I refresh, but my refresh won’t recreate cache.

So what kind of visit is gonna create new cache so I can get new copy? Does it have to be new visitor, crawler?

this query string will actually bypass both cache and page optimization , please check what is the http response header when you visit the page with this query string, looking for header x-litespeed-cache or x-litespeed-cache-control and its value

So the problem is that I moved CSS from builder (inline code) to external file in my child theme. Now when I purge ALL, purge css/js and then purge UCSS, at the end purge cloudflare (or even disable cloudflare), logged in users are still served old css. Anything I can do about it? I dont’t see a way to change version of guest js file

• This reply was modified 3 months, 3 weeks ago by mcdeth.

what happens if you just disable the litespeed cache plugin ?

and also please try in browser dev tool, search these old style CSS , see which file or where did it come from

Hi, so steps I took to test:

• Disabled cloudflare
• Disabled litespeed on both server (hostinger) and plugin
• do change in css file – set black background on a div, checked in private mode on first load, is ok
• refreshed page with ?LSCWP_CTRL=before_optm
• no change
• enabled dev tools in browser, in network tab disabled cache, refresh
• serving proper version

Server header is litespeed

HTTP/2 200 
cache-control: public, max-age=31557600
expires: Thu, 14 Aug 2025 20:36:01 GMT
content-type: text/css
last-modified: Sun, 11 Aug 2024 19:50:32 GMT
etag: "493c-66b91608-1f71d3a08d139d31;br"
accept-ranges: bytes
content-encoding: br
vary: Accept-Encoding
content-length: 3090
date: Wed, 14 Aug 2024 14:36:01 GMT
server: LiteSpeed
platform: hostinger
content-security-policy: upgrade-insecure-requests
X-Firefox-Spdy: h2

GET /wp-content/plugins/wp-loyalty-rules/App/Apps/Launcher/V2/Assets/Site/Css/launcher_site_ui.css?ver=1.2.13&t=1723646160 HTTP/2
Host: xxx
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0
Accept: text/css,*/*;q=0.1
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br, zstd
DNT: 1
Sec-GPC: 1
Connection: keep-alive
Referer: domain/page/?LSCWP_CTRL=before_optm
Cookie: 
Sec-Fetch-Dest: style
Sec-Fetch-Mode: no-cors
Sec-Fetch-Site: same-origin
Priority: u=2
TE: trailers

I am updating CSS version, but it’s not changing unless I set no cache in browser,

• This reply was modified 3 months, 2 weeks ago by mcdeth.
• This reply was modified 3 months, 2 weeks ago by mcdeth.
• This reply was modified 3 months, 2 weeks ago by mcdeth.

I can’t edit anymore. Turns out the problem was CSS version. once I made sure that it’s for example timestamp, all good