I would suggest that we resolve these issues as follows: - allow PROPPATCH to update the DAV:reftarget property - have an additional property that specifies the status that will be returned, e.g. DAV:redirectref-status that has an integer value of either 301 or 302. Cheers, Geoff Julian on 01/05/2004 07:40:42 AM: > > Hi, > > there was an outstanding issue to replace MKRESOURCE by a less generic > method that only creates redirects and does not overlap with PROPPATCH. > > This was added in the current edits at > <http://greenbytes.de/tech/webdav/draft-ietf-webdav-redirectref- > protocol-latest.html#METHOD_MKREDIRECTREF>. > > The following issues remain: > > - missing ability to update the target without having to delete and > re-create the redirect resource (proposal: just add UPDATEREDIRECTREF) > > - missing ability to create specific redirect types (such as those > generating a 301 rather than a 302) > > > Regards, Julian > > > -- > <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 >Received on Wednesday, 7 January 2004 18:14:21 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:05 GMT