|Issue 654378||Resources always read from cache even when refreshing|
|Starred by 5 users||Reported by firstname.lastname@example.org, Oct 10||Back to list|
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 https://a1.alicdn.com/oss/uploads/2016/10/10/f0844f80-8ed5-11e6-a64e-678aaf85f7c0.html 2. click the reload button What is the expected behavior? https://download-chromium.appspot.com/img/logo.png 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
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.
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 https://bugs.chromium.org/p/chromium/issues/detail?id=662007 this is a significant nuisance when developing on localhost. Please consider fixing this.
|► Sign in to add a comment|