Status: Unconfirmed Owner: ---- Labels: Type-Bug Pri-2 OS-All Area-Misc New issue 20594 by daniel.bodart: Additional Cache Control Headers in 304 request are ignored http://code.google.com/p/chromium/issues/detail?id=20594
Chrome Version : 4.0.204.0 (Developer Build 24854) URLs (if applicable) : http://www.webfabric.org/test/abc.txt Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 3: OK Safari 4: OK Firefox 3.x: OK IE 6: OK IE 7: OK IE 8: OK Opera 9.x: FAIL What steps will reproduce the problem? 1. Load any URL that supports Cache-Control directives and conditional GET via ETags/Last Modified headers 2. Reload the page after the cache expires (but without server side changes to the URL) 3. The server responds with a 304 Not Modified and a new Cache Control directive What is the expected result? As per HTTP RFC 2616 http://www.w3.org/Protocols/rfc2616/rfc2616- sec10.html#sec10.3.5 If the 304 requests contains new headers they should be used to update the cached entry. The end result should be a cycle of cache hits followed by one 304 request as follows Test URL: http://www.webfabric.org/test/abc.txt First Request => 200 OK Re-request at 0m 30s => cache hit Re-request at 1m 01s => 304 Not Modified with new Cache-Control directives Re-request at 1m 30s => cache hit Re-request at 2m 01s => 304 Not Modified with new Cache-Control directives Re-request at 2m 30s => cache hit etc etc What happens instead? After the cache expires the browser never uses the addional headers in 304 request: First Request => 200 OK Re-request at 0m 30s => cache hit Re-request at 1m 01s => 304 Not Modified with ignored headers Re-request at 1m 30s => 304 Not Modified with ignored headers Re-request at 2m 01s => 304 Not Modified with ignored headers Re-request at 2m 30s => 304 Not Modified with ignored headers etc etc Please provide any additional information below. Attach a screenshot if possible. This will make quite a big difference to performance for site that use caching and ETags, especially for low bandwidth clients. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
