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

Re: NEW ISSUE: Methods and Caching (proposal)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 19 Nov 2008 15:18:06 +0100
Message-ID: <4924201E.1070100@gmx.de>
To: Henrik Nordstrom <henrik@henriknordstrom.net>
CC: Jamie Lokier <jamie@shareable.org>, Brian Smith <brian@briansmith.org>, ylafon@w3.org, mnot@mnot.net, Robert.Siemer-httpwg@backsla.sh, ietf-http-wg@w3.org

Henrik Nordstrom wrote:
> 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.

Yes, and we will need to define what the selected representation is.

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

Sure. That would break for instance conditional headers on WebDAV 
requests, such as LOCK.

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

I may agree with this, but we certainly need to do better stating it.

BR, Julian
Received on Wednesday, 19 November 2008 14:18:51 GMT

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