Ticket #211 (closed design: fixed)
Heuristic caching of URLs with query components
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
|Component:||p6-cache||Severity:||Active WG Document|
2616 specified in 13.9
We note one exception to this rule: since some applications have traditionally used GETs and HEADs with query URLs (those containing a "?" in the rel_path part) to perform operations with significant side effects, caches MUST NOT treat responses to such URIs as fresh unless the server provides an explicit expiration time. This specifically means that responses from HTTP/1.0 servers for such URIs SHOULD NOT be taken from a cache.
- The second requirement really doesn't make much sense
- The first requirement isn't implemented by many caches, especially browser caches.
- The basis for this requirement -- that some scripts using query strings and GET have side effects -- is very old, and couched as a transitional requirement from HTTP/1.0
- There is no corresponding requirement for write-through for such requests.
Proposal: remove this requirement, replacing with an explanatory / historical note.
- Status changed from assigned to closed
- Resolution set to incorporated
- Status changed from closed to reopened
- Resolution incorporated deleted
- Status changed from reopened to closed
- Resolution set to fixed