W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2004

Re: redirect references protocol: automatic update

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Wed, 7 Jan 2004 18:16:36 -0500
To: webdav <w3c-dist-auth@w3.org>
Message-ID: <OF26CD6376.FD8D7870-ON85256E14.007E5939-85256E14.007FDD9F@us.ibm.com>

I don't see why we couldn't require this (redirects created by some other
mechanism don't have to act the same way as redirects created by 

So we could/should say that the value of a redirectref changes only when
it is explicitly updated by a PROPPATCH of the DAV:reftarget property,
and not as a side-effect of some other operation such as MOVE.


Julian on 01/05/2004 07:29:23 AM:
> Regarding issue the last call (year 2000) issue:
> <http://greenbytes.de/tech/webdav/draft-ietf-webdav-redirectref-
> protocol-latest.html#rfc.issue.lc-57-noautoupdate>
> "Add language to forbid servers from automatically updating redirect 
> resources when their targets move."
> I don't think we can forbid that. This spec consists of (a) 
> clarifications of how a server that supports redirects should behave for 

> specific WebDAV methods, and (b) extensions to explicitly create them 
> (or to apply a method to the redirect itself). As such, we shouldn't add 

> any requirements that HTTP doesn't add. What we could do is (1) note why 

> auto-update may be a bad idea, and possibly (2) define that redirects 
> created by MKREDIRECTREF should not behave that way (or alternatively 
> define more specific resource types).
Received on Wednesday, 7 January 2004 18:16:40 UTC

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