I’ve made critical updates to the js resources located at sc.itmop.com on my origin server. Despite purging the Cloudflare cache multiple times, clients are still receiving the outdated version. I’m wondering if there are any additional steps I can take to ensure that clients are served the latest version promptly.
What steps have you taken to resolve the issue?
I’ve tried clearing the cache for individual files and setting page rules, but nothing seems to be working.
There’s also a cache on the server, so you should purge that first, and then purge Cloudflare’s cache.
> GET /v1/m/statics/js/downinfo.js HTTP/2
> Host: sc.itmop.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/2 200
< date: Thu, 09 Jan 2025 04:00:13 GMT
< content-type: application/javascript
< etag: W/"677c8d5c-68044"
< last-modified: Tue, 07 Jan 2025 15:08:02 GMT
< vary: Accept-Encoding
< x-cache: HIT, policy, disk <---------- Server Cache
< cf-cache-status: HIT <-------- Cloudflare Cache
< age: 3442
Cloudflare cache pulled that file about an hour ago, but when it pulled the file from the server, it was from the server’s cache, and not a fresh copy.
When I make a request to the server with a query string to bust the cache, I get this cache status instead:
< x-cache: UPDATING
And when I diff the version in server cache vs fresh, I get this:
Thank you for your reply. However, when I bypass the Cloudflare proxy and directly access the downinfo.js file, I can get the latest version. I don’t quite understand what you mean by “Server Cache”. Could you please explain it in detail? Thank you!