Cloudflare is using old js files even after deployment and 'Purge Everything'
Hello everyone, can someone help me with this issue? A lot of clients are getting old js files which are not anymore and facing issues on the app
HHave your clients purged their caches in their browsers?
V@ilirosmanaj
Ihi @HardlyWorkin' if they purge everything (as in do a hard reload and clear cache), then it works, but it;s not really viable
Iwe have so many users that have our tooling on their websites and we cannot ask all of these users to purge their browsers
I@HardlyWorkin' any idea? We are a SaaS service and this is keeping all of our users away from using the product
HUntil their cache expires, I don't think there is much, if anything you can do.
HIf they have to revalidate before the expiration, it might go a bit faster
Dyou can change the url of the file being requested, to change the cache key
HOh yeah, that
D(this is what most modern frameworks do, hence
index-H3974.js and similar file namesHIf your HTML, or whatever is calling the JS, isn't cached too, anyway
Dso if the content changes, it's a new file and not cached
Dyeah I would advise against caching the html on client side
Iyep, we're using VITE for that, as part of our react app
II've completely removed the cloudflare from the proxy of the requests to my app, currently using for DNS only. This should also disable it fully, correct?
HNot really, unless the HTML has changed
Dthat won't help if it was cached on the client side, and also exposes your origin
Icache purging helps?
Idoes me pushing a new build help?
HOnly if the names of the JS files change
Ithey do change but I am still unable to load it
HJust to check, is the HTML being cached?
IJS files
Ithese are all minified/autogenerated ones
HNo, I mean the HTML that requests the JS files
Ino, I don't think so
I@HardlyWorkin' we're really in a bad spot and would need some help, also as paid as well. Would you be up to jumping on a call with me and our team to check this qucikly?
Imore than happy to cover your expertise on this
Isame for @PurpleBlob | Rollback if this works
DI can't jump in a call now, but happy to continue to help you :meowwink:
Don a browser that's seeing the old files, what's the local cache state? and what's the cf-cache-status header (on the html file, first)
Ithe weird thing Is that I cannot even open the network tab for that on my machine
Iit is frozen on a weird state that was loading earlier and that caching has not yet been validated
Ilet me check
D
that's weirdIcurrently I am full on cloudfront, but it still persists (as I have disabled cloudflare)
Iany ideas @PurpleBlob | Rollback ?
Ithis is what we see in one of our clients
Iit doesn't work unless you cleared the cache
Iso the status is HIT, even though caching is disabled in cloudflare
HIt's stored in the disk cache
HNo matter what settings you apply in Cloudflare, if it is cached on the client's disk, and that file is still being called, then it will be served as is
Iin the disk cache, as in the clients pc?
HThat is correct
Iok, I see 24h caching time over there
Iso there is no way we can force this caching removal from our side?
Donly if you rename the files
Dor append a querystring, like
index.js?version=2Iwe've fully removed cloudflare for now, so I guess no other way to go past it
