Opened 13 years ago

Closed 12 years ago

Last modified 11 years ago

#211 closed design (fixed)

Heuristic caching of URLs with query components

Reported by: mnot@… Owned by: julian.reschke@…
Priority: normal Milestone: 10
Component: p6-cache Severity: Active WG Document
Keywords: Cc:


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.

  1. The second requirement really doesn't make much sense
  2. The first requirement isn't implemented by many caches, especially browser caches.
  3. 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
  4. There is no corresponding requirement for write-through for such requests.

Proposal: remove this requirement, replacing with an explanatory / historical note.

Attachments (1)

i211.diff (1.3 KB) - added by julian.reschke@… 13 years ago.
proposed patch for part 6

Download all attachments as: .zip

Change History (9)

Changed 13 years ago by julian.reschke@…

proposed patch for part 6

comment:1 Changed 13 years ago by mnot@…

  • Milestone changed from unassigned to 10

comment:2 Changed 13 years ago by julian.reschke@…

  • Owner set to julian.reschke@…

comment:3 Changed 13 years ago by julian.reschke@…

  • Status changed from new to assigned

comment:4 Changed 13 years ago by julian.reschke@…

From [828]:

add note about heuristic caching when query component is present (point out the history of it) (see #211)

comment:5 Changed 12 years ago by julian.reschke@…

  • Resolution set to incorporated
  • Status changed from assigned to closed

comment:6 Changed 12 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:7 Changed 12 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed

comment:8 Changed 11 years ago by mnot@…

  • Severity changed from Candidate WG Document to Active WG Document
Note: See TracTickets for help on using tickets.