W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2010

NEW: #225: PUT and DELETE invalidation vs. staleness

From: Mark Nottingham <mnot@mnot.net>
Date: Fri, 23 Jul 2010 17:06:42 +0200
Message-Id: <8CAE11BF-9CD9-4087-968F-70D67E7A86A5@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>
<http://trac.tools.ietf.org/wg/httpbis/trac/ticket/225>

p2 7.6 (PUT):

If the request passes through a cache and the Effective Request URI identifies one or more currently cached entities, those entries SHOULD be treated as stale.

p6 2.5 (Request Methods that Invalidate):

Here, "invalidate" means that the cache will either remove all stored responses related to the Effective Request URI, or will mark these as "invalid" and in need of a mandatory validation before they can be returned in response to a subsequent request.

These sections conflict regarding the side effects of PUT; p2 only wants it marked stale, whereas p6 says it cannot be served stale, but must (at least) be revalidated.

The same problem holds for DELETE.


---

One point of data: Squid invalidates (i.e., removes from cache) as a side effect of PUT/DELETE, although IIRC this is only in Squid-2.HEAD. 

Opinions?

--
Mark Nottingham     http://www.mnot.net/
Received on Friday, 23 July 2010 15:07:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:23 GMT