I configuration webdav on nginx/gentoo. But when I connect to my server, I got this error (I logging in with cyberduck from mac

PROPFIND /mydavserver HTTP/1.1[\r][\n]
Authorization: Basic d2F4Om9qa2l5ZA==[\r][\n]
Content-Type: text/xml; charset=utf-8[\r][\n]
User-Agent: Cyberduck/3.3b4 (5455)[\r][\n]
Host: 192.168.0.28:8088[\r][\n]
Content-Length: 207[\r][\n]
Depth: 0[\r][\n]
[\r][\n]
HTTP/1.1 405 Not Allowed[\r][\n]
HTTP/1.1 405 Not Allowed[\r][\n]
Server: nginx/0.8.29[\r][\n]
Date: Mon, 11 Jan 2010 04:19:11 GMT[\r][\n]
Content-Type: text/html[\r][\n]
Content-Length: 173[\r][\n]
Connection: keep-alive[\r][\n]
Keep-Alive: timeout=20[\r][\n]
[\r][\n]

How do i solve this problem ?

thanks.

For WinXP mounting, this patch needs to be applied:
In davserver.py replace line 254 with the following:
w.write(‘%s\n’ % urllib.quote(m.virname))

With the fixed pandav, most everything seems to work right with Windows’ DAV client, and Nginx still handles GET/PUT if
using (OPTIONS|PROPFIND|LOCK|UNLOCK|PROPPATCH|HEAD|MKCOL|COPY|MOVE)
However, windows doesn’t send requests about folders with the HTTP spec’d trailing slash (“/mydir” vs. “/mydir/”) . Most items in the nginx dav code say to send 409 to DAV operations on
folders if they are missing the slash. Normally, for a human using a web browser, the web server sends a redirect to fix the path to proper spec but if you try to do that to a broken dav client, you get a whole other type of error. If nginx can get a
little more flexible about folders (like apache’s “redirect-carefully”), WinXP should be all set.

I have not tested pandav with svn/git/cadaver/nd ….

that if condition should be:

if ($request_method ~ ^(PROPFIND|OPTIONS|PROPPATCH|LOCK|UNLOCK)$ ){
... }


Also, that webdev.cgi is actually pretty weak, it only does PROPFIND. I’m gonna try libhttp-davserver-perl’s nph-webdav and see if that does a bit more.