Force reload (shift+enter) doesn't reload some resources
Reported by
human.p...@gmail.com,
Mar 24 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.33 Safari/537.36 Example URL: Steps to reproduce the problem: I tried to reduce the repro steps to a simpler one, but failed. So, below is my original steps, which requires a Wikipedia account. 1. Go https://en.wikipedia.org/wiki/Main_Page and log in. 2. Go to https://en.wikipedia.org/wiki/User:<your username>/common.js to add: mw.loader.load('https://wikiplus-app.smartgslb.com/Main.js'); (This is just a small tool to help quick edit Wikipedia. You can investigate the source code first if you're suspicious.) 3. Now, go to any Wikipedia page and open Network tool. You will see it should try to load a CSS file called "Wikiplus.css". 4. Force reload (shift+F5) the page with the Network panel open. What is the expected behavior? The Wikiplus.css file should be reloaded from the server. What went wrong? It didn't. After shift+F5, it still says "(from disk cache)" and I can confirm it's actually not refreshed (because before, the author of Wikiplus updated the CSS file on his server. But it doesn't refresh on my end even if I shift+F5'd). Did this work before? N/A Chrome version: 58.0.3029.33 Channel: beta OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Note: the "Disable cache" option in the Network tool works fine. If you enable that, even a normal refresh (F5) will reload the CSS resource here. But the problem here is why shift+F5 doesn't do the similar.
,
Mar 24 2017
I've noticed this behavior when issue 612701 landed.
,
Mar 24 2017
I guess the reason is that after the load event is fired, the hard reload no longer takes effect
,
Mar 24 2017
Thanks for the report! Updating labels, as decisions to force cache revalidation on hard-reload are made in the renderer process.
,
Mar 24 2017
As mentioned at comment 4, reload does not affect resources that are triggered after the load event. Chrome have taken this behavior from the beginning, and does not related to the change of issue 612701. This behavior is reasonable for users when we consider modern sites such as single page applications. DevTools is for developers. It's useful for them to disable cache always when they need. Actually, I notice one bug that is related to hard-reload. But it is an issue that Chrome use "max-age=0" instead of "no-cache" for some rare cases, conditional requests for the main resource.
,
Mar 24 2017
How do users reload cached resources then? I report this problem exactly because I, as a user (not a developer), can't reload that particular css file to newest version, and therefore encountered weird behaviors in usage.
,
Mar 24 2017
Web site authors should design the page correctly so that users can take the latest contents when users need. HTTP/HTML specs provide several choices to realize that. Rephrasing it, specs allow web authors to design a page that avoid users unexpected reload, and I don't think adding a backdoor to the browser is a good idea. 20 years ago, we use reload as a kind of debugging tool. But it isn't any more, and DevTools is there instead.
,
Mar 24 2017
# How do users reload cached resources then? mw.loader.load() should add a cache-busting parameter (e.g. ?t=1490335176127) my opinion is website should not rely on users' reload behavior to get the latest content, no matter f5 or shift+f5, also see issue 701323 . |
|||
►
Sign in to add a comment |
|||
Comment 1 Deleted