https://issues.apache.org/bugzilla/show_bug.cgi?id=56162
Sebb <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW --- Comment #10 from Sebb <[email protected]> --- I think the cache referred to in the RFC is a proxy cache. Local caching (in the UA) is not quite the same. The decription of CM agrees with its behaviour, but that behaviour may be incorrect ... The HC4 code now has a Caching implementation; hopefully we can use that when we upgrade to the next release. However that may not be usable with the other HTTP implementations. In the meantime, I think we need to check the method as well as the status. We certainly want to cache GET. Not sure about HEAD, might be useful not to cache that as it is a way of testing the connection. And some methods we don't want to cache: PUT, POST, DELETE Perhaps we need a list of which ones to cache; this could be overridable. Also, maybe there should be an "Ignore Cache" option. This would correspond with the browser Shift-Reload feature to bypass the cache. Not sure if this should first remove any existing cache entry in case the request fails, or only update the cache on a successful response. I expect either of those would address your use-case. -- You are receiving this mail because: You are the assignee for the bug.
