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:
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).
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.
CLosed with no change.