Comment #66 on issue 2636 by bugdro...@chromium.org: Cache form data so
edits are not lost if you naivgate and then come back
http://code.google.com/p/chromium/issues/detail?id=2636
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=12374
------------------------------------------------------------------------
r12374 | da...@chromium.org | 2009-03-24 11:20:06 -0700 (Tue, 24 Mar 2009)
| 8 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/base/upload_data.h?r1=12374&r2=12373
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/http/http_cache.cc?r1=12374&r2=12373
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/http/http_cache.h?r1=12374&r2=12373
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/http/http_cache_unittest.cc?r1=12374&r2=12373
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/http/http_request_info.h?r1=12374&r2=12373
Net module changes to support caching responses to a POST request.
The solution is to add a user-defined identifier to UploadData. If that
identifier is set, and if the request method is POST, then HttpCache will
enable caching for the response. (The cache key will be a composition of
the identifier and the URL.) A subsequent POST request to the same URL
with the same identifier will "hit" the previously generated cache entry.
Reuse from the cache is subject to all of the standard rules.
BUG=2636
R=wtc
Review URL: http://codereview.chromium.org/52028
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
