cannot force chromium to update cached files
Reported by
fredrick...@gmail.com,
Mar 3 2017
|
|||
Issue descriptionChrome Version: Version 55.0.2883.75 built on Debian stretch/sid, running on Debian stretch/sid (64-bit) <b>Chrome OS Version: <From about:version: Platform x.x.x.x></b> <b>Chrome OS Platform: <Make/model of computer running Chrome OS></b> <b>Network info: <network, encryption type, router model (if known)></b> Steps To Reproduce: (1) visit site with background image to cache image (2) change image on the site (3) visit site again and new image is ignored. User is forced to clear entire cache to force chromium to reload background image! Expected Result: chromium should find and display ANY updated files! Actual Result: site changes cannot be viewed unless user is willing to clear his browsers cache every time he wants to see new or modified content. How frequently does this problem reproduce? Always What is the impact to the user, and is there a workaround? If so, what is it? makes USER's life miserable and unproductive
,
Mar 9 2017
fredrick.o.jackson: Could you please reply to comment #1? If the issue is just normal reloads not revalidating all resources, that's expected behavior (And respecting cache headers on normal reloads results in significant bandwidth savings), and unlikely to be changed.
,
Mar 9 2017
Not the OP, but I encountered same problem lots of times: some resources won't be reloaded even if I hard reload.
It's pretty common for files that are loaded by other file (like JS, CSS files).
Here is an example: I have a JS that will load a CSS file:
//载入CSS
$("head").append("<link>");
$("head").children(":last").attr({
rel: "stylesheet",
type: "text/css",
href: scriptPath + '/wikiplus.css'
});
(part of the code)
But the problem here is this CSS file will not be reloaded if I hard reload it. It still shows "from disk cache" in the Network panel in the Dev Tool.
,
Mar 9 2017
human.peng: By "hard reload", I assume you mean shift+reload? Anyhow, this seems more of a Blink>Loader issue than a cache issue - the loader is what decides which resources to bypass the cache on.
,
Mar 10 2017
Yeah I mean shift+F5 (or Ctrl+F5).
,
Mar 10 2017
human.peng: Thanks for the followup! Mind filing a new bug about that? I think we have some sort of heuristics about when the reload ends, and I suspect you're running into an issue there, which is a bit different from what this bug is about. Post the bug number here or email it to me, and I'll attack the appropriate labels.
,
Mar 23 2017
human.peng: ping
,
Mar 24 2017
Sorry for being late. I was trying to make a simpler STR but failed. So here we go, the original scenario I encountered: issue 704802 .
,
Apr 7 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jkarlin@chromium.org
, Mar 3 2017