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

Invalidation after updates or deletions

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 17 Jul 2006 21:36:42 -0700
Message-Id: <8C0F94B4-8362-4483-A6C6-B9C2C60ECA5B@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>

RFC2616 says that POST, PUT, DELETE and unrecognised request methods  
passing through a cache MUST invalidate one or more cache entries  
(depending on the values of the Location and Content-Location headers).

   http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.10

In my informal (and not yet complete) testing, I've only found one  
cache implementation -- client or intermediary -- that actually does  
this. I've tried to engage various vendors, etc. to fix it, but  
haven't seen much interest.

Why is that? Is there some non-obvious impediment to implementation?  
Lazy developers?

If it doesn't see any take-up, perhaps it should be deprecated, or  
relegated to a cache extension; e.g.,

Cache-Control: no-cache, max-age-if-you-actually-invalidate=300

Thoughts?

--
Mark Nottingham     http://www.mnot.net/
Received on Tuesday, 18 July 2006 04:36:50 GMT

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