Updates:
Status: WontFix
Cc: [email protected]
Comment #7 on issue 2340 by [email protected]: Images don't display when
server replies 304 not modified with a no-cache no-store directive
http://code.google.com/p/chromium/issues/detail?id=2340
Setting no-store in the 304 response is rather interesting use-case.
I tested with the latest version of Chrome (4.0) and it seems to be working.
When getting the "no-store" in the 304, it dooms the cache entry.
This makes it so the current request still serves the cached data, but the
next request will result in a cache miss.
So as you refresh continually, 50% of loads re-download the content, and
50% serve from cache.
Note that the original URLs in this bug report don't seem to behave as
described anymore, so I am attaching a test-page which
reproduces the setup. (if you are on the google corp network you can also
access it at
http://www/~ericroman/nostore304.php).
Closing this bug as fixed.
cc-ing Ricardo in case I missed something.
Attachments:
nostore304.php 820 bytes
--
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
