Cannot get rid of cached file no matter what
Reported by
david.kr...@gmail.com,
Jul 27 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 Steps to reproduce the problem: 1. Website doesn't work because Chrome (in developer tools) sees the old version of javascript file... I tried EVERYTHING, disabling cache, clearing cache etc, nothing helps... and when I visit that file directly I see the new version WEIRD and frustrating :) 2. 3. What is the expected behavior? it should (eventually) or IMMEDIATELY (shift+refresh) get the fresh file... What went wrong? File stuck inside Chrome cache, I'm not even sure new one will appear if I wait for 10 years. Did this work before? N/A Chrome version: 52.0.2743.82 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 22.0 r0 arrrrghh
,
Jul 27 2016
I could fix this ONLY by going into DEV mode on CloudFlare I did purge the cache on cloudflare before, didn't help.. this really is some problem in Chrome because as I said curl and also chrome itself showed the new version when going to example.com/js/script.js directly... just Dev Tools (and rendering engine itself) always saw the old file... Not sure how to go about investigating this... I noticed script tag had data-rocketoptimized attribute, then remembered cloudflare (Rocket loader is from them), and decided to enable dev mode there.. this FINALLY helped...
,
Jul 28 2016
Can you provide us the website?
,
Jul 29 2016
,
Jul 29 2016
This is almost certainly not a Chrome issue. I can just say that from having seen a bunch of issues claiming that the cache was storing/not storing things incorrectly, and after a deep dive, they're pretty much always either broken sites, or people not understanding expected caching behavior. That having been said, if you provide log, following the instructions here, we can take a look: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details Just so we can see the initial response from the server, please clear your cache (Either using the little down arrow at the upper right in about:net-internals, or from the settings page).
,
Aug 29 2016
No feedback was received in the last 30 days from reporter "david.krmpotic@gmail.com", so archiving this. Please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by david.kr...@gmail.com
, Jul 27 2016