New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 654378 link

Starred by 5 users

Issue metadata

Status: WontFix
Closed: Oct 2016
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Sign in to add a comment

Resources always read from cache even when refreshing

Reported by, Oct 10 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2885.0 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. open demo
2. click the reload button

What is the expected behavior? request should be '304'

What went wrong?
 (from memory cache)

Did this work before? N/A 

Chrome version: 56.0.2885.0  Channel: n/a
OS Version: OS X 10.10.4
Flash Version: Shockwave Flash 23.0 r0
Components: Blink>Loader
We have been experimenting with a new reload, which only force revalidates the main resource (rather than all subresources).

+toyoshim who is working on this feature.
Apply Cache-Control: immutable ( issue 611416 ) for all subresources by default? too aggressive IMO.

Comment 3 by, Oct 10 2016

Components: -Internals>Network
Status: Assigned (was: Unconfirmed)
Labels: -OS-Mac OS-All
Status: WontFix (was: Assigned)
Reg #2.

No, originally Chrome sent 'Cache-Control: max-age=0' for all resources in reloads. This was too aggressive today because now developers have the Inspector as a right tool to debug the web.

After the modification, Chrome sends it only for the main resource, but just follows the protocol for sub-resources. That means Chrome will uses cached contents only when the cached contents are allowed to be reused, e.g. not expired.
 Issue 662007  has been merged into this issue.
Hi, as I mentioned in

this is a significant nuisance when developing on localhost. Please consider fixing this.

Sign in to add a comment