Comment #11 on issue 20594 by [email protected]: Additional Cache
Control Headers in 304 request are ignored
http://code.google.com/p/chromium/issues/detail?id=20594
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=25540
------------------------------------------------------------------------
r25540 | [email protected] | 2009-09-04 15:51:53 -0700 (Fri, 04 Sep 2009)
| 9 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/http/http_response_info.h?r1=25540&r2=25539
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/url_request/url_request.h?r1=25540&r2=25539
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/url_request/url_request_unittest.cc?r1=25540&r2=25539
Re-enabled URLRequestTestHTTP.BasicAuth.
The problem was the test was expecting |response_time| of cached responses
to be the timestamp of the original request, rather than the timestamp of
the last cache validation.
Also updated the header to clarify what |request_time| and |response_time|
correspond to in the cached cases.
BUG=http://crbug.com/20594
Review URL: http://codereview.chromium.org/197030
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
