W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2008

Re: NEW ISSUE: Methods and Caching

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Thu, 20 Nov 2008 10:55:17 +0100
To: stefan.eissing@greenbytes.de
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Brian Smith <brian@briansmith.org>, mnot@mnot.net, ietf-http-wg@w3.org
Message-Id: <1227174917.20064.32.camel@henriknordstrom.net>
On tor, 2008-11-20 at 10:19 +0100, stefan.eissing@greenbytes.de wrote:

> So, the cache is caching resource representations, not responses to
> specific request types. There is no cached response for a POST, separate
> to a cached response to a GET and to a PATCH and so forth. Instead the
> cache is holding at most *one* entry per URI.

per Content-Location URI, when Content-Location is given.

For any given Request-URI there MAY be many variants, each of which MAY
have a unique Content-Location, and servers SHOULD provide this (unique
locations) if they can.

Some methods or responses return the complete representaion, some only
partial headers and/or partial body.

> Unsafe methods like POST clear the cache for the request URI, before any
> processing is done. Which enforces a cache miss and a forwarding of the
> request to the server (or up the cache chain).

Yes.

> Would that describe the principal operation of a HTTP cache (ignoring
> all the fine details of cache-control and so forth)?

In my view yes.

Regards
Henrik

Received on Thursday, 20 November 2008 09:56:10 GMT

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