Jim, > It seems to me that it's possible to configure a WebDAV server > such that it doesn't support redirect reference resources, but > does give out 302s for some URLs. I think that's just a matter of what you mean by "support redirect reference resources". If it can return 302s, it knows about redirects. It may not support to *author* them, but that's a separate issue. > I'm fine with saying MKCOL, like all methods, is redirected by 302. So what does this mean? If a client does a MKCOL on a URI and receive a 302 with Location header, what is it supposed to do? a) consider this a failure, just as a 405 (resource exists) b) redirect the MKCOL to the URI specified in the Location header? IMHO, the answer must be a), thus the request is not really redirected -- it just fails, because the resource identified by the request URI already exists, and MKCOL is defined only to suceed on null resources. Julian -- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760Received on Friday, 27 June 2003 03:53:06 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:29 UTC