Sounds like a bug in mod_dav, although the 301 response is a bit unusual IMO.
>From rcf2518 section 5.2: 'There is a standing convention that when a collection is referred to by its name without a trailing slash, the trailing slash is automatically appended. Due to this, a resource may accept a URI without a trailing "/" to point to a collection. In this case it SHOULD return a content-location header in the response pointing to the URI ending with the "/". For example, if a client invokes a method on http://foo.bar/blah (no trailing slash), the resource http://foo.bar/blah/ (trailing slash) may respond as if the operation were invoked on it, and should return a content-location header with http://foo.bar/blah/ in it. In general clients SHOULD use the "/" form of collection names.' Regards Tim > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 16, 2002 12:28 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Interoperability of WebDAV client and Apache 2.0 mod_dav > > > Hi all, > > sending a PROPFIND request on a collection to mod_dav without a trailing > slash in the URL results in a 301. Since WebdavResource.listWebdavResource > () does exactly this, it does not work with mod_dav. > > Can this be fixed/worked around in Slide WebDAV client or is it a bug of > mod_dav? > > Thanks for any hint > Guido > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
