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

Re: NEW ISSUE: Methods and Caching (proposal)

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Wed, 19 Nov 2008 14:35:14 +0100
To: Jamie Lokier <jamie@shareable.org>
Cc: Brian Smith <brian@briansmith.org>, ylafon@w3.org, mnot@mnot.net, Robert.Siemer-httpwg@backsla.sh, ietf-http-wg@w3.org
Message-Id: <1227101714.8203.14.camel@henriknordstrom.net>
On ons, 2008-11-19 at 12:15 +0000, Jamie Lokier wrote:

> 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.

etag values in requests refer to the "selected representation", not the
method specific response.

Basing the selected representation on the method used does not make much
sense imho. 

ETag headers in responses also refer to the selected representation the
response either contains or relates to, and is meant to be able to use
as validator cross methods for the same URI.


Received on Wednesday, 19 November 2008 13:36:02 UTC

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