W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005

Re: Summary of ETag related issues in RFC2518bis

From: Wilfredo Sánchez Vega <wsanchez@wsanchez.net>
Date: Mon, 19 Dec 2005 17:13:39 -0800
Message-Id: <DCEC167B-F3EA-4D77-913F-694D618A9225@wsanchez.net>
Cc: Julian Reschke <julian.reschke@gmx.de>, w3c-dist-auth@w3.org
To: Jim Whitehead <ejw@soe.ucsc.edu>

   The second option seems impossible.  If modifying the last- 
modified time on an HTTP entity MUST change the etag and modifying  
DAV:getlastmodified MUST NOT, that's contradictory, give the  
definition of DAV:getlastmodified.

   I don't think any of these three options makes sense as a  


On Dec 19, 2005, at 1:20 PM, Jim Whitehead wrote:

> It seems to me we have a few choices.
> * Stick closely to the HTTP notion of entity, in which case changes  
> to the DAV:getcontentlanguage, DAV:getcontenttype,  
> DAV:getcontentlength, and DAV:getlastmodified MUST affect the Etag,  
> and changes to other properties MUST NOT affect the etag.
> * Make a clear distinction between WebDAV properties and HTTP  
> entities, stating that changes to WebDAV properties MUST NOT cause  
> changes to HTTP entities.
> * Consider WebDAV properties to be part of the state of the  
> resource, even though they (except for the properties listed above)  
> do not affect the entity (as defined by HTTP), and hence any change  
> to a property MUST cause a change to the Etag.
> I'll note that the third option seems to be the hardest one to  
> defend based purely on the language of the HTTP specification.
Received on Tuesday, 20 December 2005 01:13:55 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:34 UTC