httpbis: Ticket #23: no-store invalidation

Link:  http://trac.tools.ietf.org/wg/httpbis/trac/ticket/23

Origin:  http://lists.w3.org/Archives/Public/ietf-http-wg/2005JulSep/0004.html

Component: p6-cache

Responses to HTTP requests with "Cache-control: no-store" are not cachable. Recently, we came across a cache that does not cache responses to no-store requests but also does not invalidate an older cached entity with the same URL. When future requests stop using no-store, the old cached entity is served.

For example, the following happens in our test case:

  1. Client requests an entity A without using no-store.
  2. Cache proxies the transaction and caches the response (entity A).
  3. Client requests the same entity A using "Cache-control: no-store".
  4. Cache proxies the transaction and does NOT cache the response.
  5. Client requests the same entity A again, without using no-store.
  6. Cache serves the "old" entity A cached in step #2 above.

Does the cache violate the intent of RFC 2616 in step #6? If yes, should that intent be made explicit (I cannot find any explicit rules prohibiting the above behavior).

Mails

Mails by Sender (Top 10) Mails by Month

History

: comment added; version, component, milestone set (Fri, 04 Jan 2008 06:17:58 GMT)

: comment added (Tue, 05 Feb 2008 03:46:10 GMT)

I don't see any intent being violated in that example. An HTTP server must be able to interpret each request in isolation (HTTP is stateless by definition), so it really doesn't matter what requests came before the one which is answerable from the cache.

IMO, no change is needed.

: comment added; resolution set; status changed (Mon, 26 May 2008 11:40:41 GMT)

CLosed with no change.

Related Information

Issues List Index