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

Re: NEW ISSUE: Methods and Caching (proposal)

From: Jamie Lokier <jamie@shareable.org>
Date: Wed, 19 Nov 2008 12:15:46 +0000
To: Brian Smith <brian@briansmith.org>
Cc: henrik@henriknordstrom.net, ylafon@w3.org, mnot@mnot.net, Robert.Siemer-httpwg@backsla.sh, ietf-http-wg@w3.org
Message-ID: <20081119121545.GB22269@shareable.org>

Brian Smith wrote:
>      + For methods other than GET and HEAD, a cache
>      + MUST forward the request to the origin server
>      + and MUST return the origin server's response.
>      + For GET and HEAD requests, a cache MUST 
>      + response with the most up-to-date
>      + Responses for methods other than HEAD and GET
>      + MUST NOT be cached.

Provided we understand that at some point, we _might_ define
cachability of some other methods when the response contains a
"Cache-Control" header, maybe with a yet to be defined token.

There is no harm in other method responses being cachable if the
server says they are, especially if an Etag is used so the origin
server is always consulted for accuracy.

-- Jamie
Received on Wednesday, 19 November 2008 12:16:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:10:47 UTC