Impossible to cahce-bust
Reported by
pingram3...@gmail.com,
Aug 2
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36 Steps to reproduce the problem: 1. Difficult to reproduce but happens frequently 2. Make changes to css file 3. Reload after exhausting all cache-busting efforts, Chrome specifically still loads old css file (unless you add a query string or change file name) What is the expected behavior? Expected behavior when Disable Cache when Dev Tools is open is enabled is zero caching in browser 100% What went wrong? 1. Made a simple css edit. 2. Reload web page, edit not reflected proven when inspecting code 3. Load direct url to css file, still shows old version 4. Look at file directly on web server, definitely new version 5. Verified no external caching services ie cloudflare, etc 6. Verified no server side caching services, varnish, etc 7. Also tried "Empty Cache and Hard reload" from Refresh right-click menu 8. Tried logging out of all google accounts in Chrome 9. Tried incognito tab 10. Opened both the web page and the direct url to css file in any other browser and it loads the current (proper) version of css file 11. Back to square one, open direct url of css file in Chrome again, still previous version 12. Add any query string to css file, loads new version, remove query string loads previous version Did this work before? N/A Chrome version: 68.0.3440.75 Channel: stable OS Version: OS X 10.12.5 Flash Version: Shockwave Flash 30.0 r0 something is caching beyond what is being told to us web developers. We absolutely must have a way to clear ALL caching mechanisms otherwise troubleshooting is futile
,
Aug 8
Thanks for the issue. @reporter : Could you please provide a sample file or an url that reproduces the issue, so that it would be really helpfull for further triaging. Thanks.!
,
Aug 8
With the nature of "caching" it is only temporary and always seems to resolve itself after a short (unknown) time and since I don't have control of the caching mechanism nor even know where it is sourced from, any url I provide will likely not be reviewed in time to see the issue in action. The best idea I have is to use screen shots to highlight the css differences between browsers. I'll try to do this and report back unless you have a better suggestion. Thanks.
,
Aug 8
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 16
pingram3541@ Thanks for the update. As per comment #3, can you please provide an update which will help us in further triaging. Thanks..
,
Aug 25
,
Oct 12
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Aug 3