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

Re: Summary of ETag related issues in RFC2518bis

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Wed, 21 Dec 2005 11:14:35 -0500
To: " webdav" <w3c-dist-auth@w3.org>
Message-ID: <OFDAAE9732.7E0F1D82-ON852570DE.00590D8F-852570DE.00593A1E@us.ibm.com>
Julian Reschke <julian.reschke@gmx.de> wrote on 12/21/2005 11:07:00 AM:

> Geoffrey M Clemm wrote:
> > Julian Reschke <julian.reschke@gmx.de> wrote on 12/21/2005 10:02:23 
AM:
> >  > 2) It seems to me that we can't rule out that servers touch the 
ETag
> >  > upon PROPPATCH (for instance, because they are indeed updating 
metadata
> >  > in the file content, such as with XMP). In which case telling the 
server
> >  > to return the new ETag upon PUT seems to be a very good idea.
> > 
> > Did you mean, return the new ETag upon PROPPATCH?
> 
> Yep. Thanks for the correction :-)

In that case, yes, I agree.

Also note that there is no issue wrt PUT-content vs. GET-content for
PROPPATCH, so that happily that issue does not arise for a PROPPATCH
etag (:-).

Cheers,
Geoff
 
Received on Wednesday, 21 December 2005 16:15:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:12 GMT