Response with Cache-Control:no-store doesn't display source on initial load
Reported by
zac.spit...@gmail.com,
May 11 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3094.0 Safari/537.36 Steps to reproduce the problem: 1. open the problem page (will provide via email), open dev tools 2. click html file in Network tree What is the expected behavior? the source for the html should be displayed What went wrong? the sources panel is blank, just showing 1 in the gutter with subsequent reloads of the page being inspected, the html source displays in devtools Did this work before? No Chrome version: 60.0.3094.0 Channel: canary OS Version: 10.0 Flash Version: I tried to reproduce a test case but wasn't able to, send me an email for a link to the problem page
,
May 12 2017
,
May 12 2017
Swapping Cache-Control: no-store for Cache-Control: private resolves this problem.
,
May 12 2017
This seems like the same thing as https://bugs.chromium.org/p/chromium/issues/detail?id=649047#c2 although it seems like we should at least show some error text in this scenario.
,
May 31 2017
Friendly ping to get an update on this issue. Thank you..!!
,
Jun 3 2017
,
Jul 20 2017
Because of performance reason chrome will not hold resources if they are no longer used. Devtools gets around this by forcing them to be held while devtools is opened. It's fairly well known that users must reload/navigate their page while devtools to get all resource info. Thanks for the bug though!
,
Jul 20 2017
Do the Developer Tools /know/ that the file is missing? If so, could we have the Developer Tools explicitly inform the user that they need to reload instead of hoping that they somehow knew this already? |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by agektmr@chromium.org
, May 12 2017Labels: OS-Mac