There should be a --no-cache flag to disable cache from being saved
Reported by
93m4qau...@gmail.com,
Jan 3 2018
|
|
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Example URL: N/A Steps to reproduce the problem: N/A What is the expected behavior? Since there isn't a setting to disable cache, at least there is a --no-cache flag to disable cache from being saved. What went wrong? There is neither a setting to disable cache nor a flag to disable cache. Did this work before? No Chrome version: 63.0.3239.108 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: It's frustrating when sites are frequently being crippled by cache, and each time you have to go to chrome://settings/clearBrowserData to fix the problem (and not so, soon afterwards).
,
Jan 3 2018
Do you know of any extensions that block caching?
,
Jan 3 2018
No, I don't. I believe all a WebRequest extension would need to do in order to manage that is attach a "cache-control: no-cache" header to all outgoing requests (Modifying the cache-related response headers wouldn't work, because extensions are hooked up at a higher layer than the cache). |
|
►
Sign in to add a comment |
|
Comment 1 by mmenke@chromium.org
, Jan 3 2018Labels: -Type-Bug Type-Feature
Status: WontFix (was: Unconfirmed)