Description: ------------ For regular files, the trailing slash in directory names is optional. E.g. is_dir('/tmp') and is_dir('/tmp/') are equivalent. With HTTP_WebDAV_Client the trailing slash is required. E.g. if file_exists('webdav://exampel.com/foo/') returns true, then file_exists('webdav://exampel.com/foo') returns false. For consistency with the filesystem, I think HTTP_WebDAV_Client should support both variants. As a quick fix I have added the following the following to _check_options(): $req->sendRequest(); + if ($req->getResponseCode() == 301) { + $this->url .= '/'; + return $this->_check_options(); + } if ($req->getResponseCode() != 200) { return false; }

Which server are you getting the 301 response from? I didn't expect a webdav server to issue redirect response headers ... but these might actually be valid and so need to be handled indeed (Note to self: check whether HTTP_WebDAV_Server should redirect on collection without trailing slash, too ...)

In RFC2616 section 10.3, the spec says: "The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD." If you're using Apache httpd, consider using "redirect-carefully" environment variable: http://httpd.apache.org/docs/2.2/en/env.html#redirect-carefully

I think HTTP_WebDAV_Client MAY handle redirections as what is done in http stream wrapper. http://www.php.net/manual/en/context.http.php#context.http.max-redirects

Marking as a wontfix for the moment, because it hasn't moved in ~6 years. Patches/pull requests welcome.