Cache shows completely different data (Chrome only)
I was using it well before.
I didn't change the source code at all, but the cache has been showing different data for about 3 hours.
I tried putting in parameters as a test, but when I request a js file or a css file, it returns an image file or completely different data.
The cache says HIT, but it's completely different data.
The same thing happens when I access it in mobile Chrome private mode.
It seems like this problem doesn't happen to everyone.
The js file is a static file. Why is this happening?
If I remove the cache from cloudflare, different data is displayed.
I attached a screenshot of when I accessed it in Chrome and when I accessed it in Firefox.
https://a.aagag.com/js/AAGAG.js?v=1
https://a.aagag.com/js/AAGAG.js?v=2
https://a.aagag.com/js/AAGAG.js?v=3
6 Replies
This issue occurs not only in js files but also in all css images.
It seems that Cloudflare's cache system is behaving strangely.
Results of cdn-cgi/trace
colo=SJC-PIG
sliver=010-pig02
The error occurs only in the part where colo is SJC-PIG. (When I change the settings to another domain and connect, I can connect normally LAX)
I tried upgrading to the pro plan to try to fix this issue, but it didn't work.
When applied to another domain with the same settings, it works properly.
https://a.gguggu.com/js/AAGAG.js?v=1
https://a.gguggu.com/js/AAGAG.js?v=2
https://a.gguggu.com/js/AAGAG.js?v=3
After upgrading to the pro plan, it changed to LAX after about 30 minutes and is now working normally. Is there a difference between free and paid?
are there any pro plan hidden perks?
I don't know either.
When visitors complained about an issue when accessing, I asked them to send cdn-cgi/trace, and the colo was always SJC-PIG.
10%~20% of users were having the issue,
and after changing to the pro plan, the issue went away.
interesting