W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2003

RE: Changing etag and getlastmodified on move/rename

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 7 Aug 2003 09:03:36 +0200
To: "Lisa Dusseault" <lisa@xythos.com>, "Webdav WG" <w3c-dist-auth@w3c.org>
Message-ID: <JIEGINCHMLABHJBIGKBCEEINIBAA.julian.reschke@gmx.de>

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Lisa Dusseault
> Sent: Thursday, August 07, 2003 1:13 AM
> To: Webdav WG
> Subject: Changing etag and getlastmodified on move/rename
> What's the general behavior for changing etag and getlastmodified 
> when a resource is simply renamed via a MOVE, or when it's moved 
> to another directory?  
> Do any clients benefit if the ETag is the same after a MOVE?
> Would the client get confused if the ETag is the same but the 
> getlastmodified value is different after a MOVE?

It shouldn't. Also, the other combination can occur as well (ETag changes, but getlastmodified doesn't). This is because the ETag must be unique for all representations produced for a particular URL (+ variant-selecting headers), *not* the resource.


/a/b with etag "1"
/a/c with etag "1"
MOVE /a/b -> a/c

The resulting ETag for "/a/c" MUST NOT be 1.

If a server needs a way to robustly identify a resource indepedantly of the URL, it should use DAV:resource-id.


<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 
Received on Thursday, 7 August 2003 03:03:56 UTC

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