Lighttpd

I am also having an issue with drag-copying a file (win_step4.png) into the Connecting folder from my desktop.

75.34.31.39 MYSERVER.mit.edu test [11/Feb/2011:01:33:13 -0500] "PROPFIND /.git HTTP/1.1" 404 345 "-" "Microsoft-WebDAV-MiniRedir/6.1.7600" 
75.34.31.39 MYSERVER.mit.edu test [11/Feb/2011:01:33:13 -0500] "PROPFIND / HTTP/1.1" 207 7976 "-" "Microsoft-WebDAV-MiniRedir/6.1.7600" 
75.34.31.39 MYSERVER.mit.edu test [11/Feb/2011:01:33:13 -0500] "PROPFIND /Connecting/win_step4.png HTTP/1.1" 207 630 "-" "Microsoft-WebDAV-MiniRedir/6.1.7600" 
75.34.31.39 MYSERVER.mit.edu test [11/Feb/2011:01:33:13 -0500] "LOCK /Connecting/win_step4.png HTTP/1.1" 409 343 "-" "Microsoft-WebDAV-MiniRedir/6.1.7600" 
75.34.31.39 MYSERVER.mit.edu test [11/Feb/2011:01:33:20 -0500] "PROPFIND / HTTP/1.1" 207 7976 "-" "Microsoft-WebDAV-MiniRedir/6.1.7600" 

I think it has to do with the 409 error issued with the LOCK request.
It may be related to issue #1953, as I suspect that Windows is sending these LOCK requests without specifying a Depth header. For regular files, lighty can handle Depth: Infinity like it handles Depth 0, and should do that instead of erroring out. I think there's a patch mentioned in that issue. Has that been merged into newer versions of 1.4?

Most of my users are using Windows as their DAV client, so this is kind of a showstopper for me.

omegaworks wrote:

I'm having an issue with mod_webdav and lighty 1.4.22

You might want to try 1.4.28.

lighttpd/1.4.28 (ssl) - a light and fast webserver
Build-Date: Nov 21 2010 06:41:02

Updated to 1.4.28 offered by latest ubuntu release, still having problems with saving and drag-copy.

@omegaworks, as you pointed out, the problem looks to be the Depth: infinity lock requests.
lighttpd mod_webdav.c does not support Depth: infinity, and if Depth header is not provided, Depth: infinity is the default.

Since this ticket is many years old, I presume you have found a different solution, presumably using a more RFC compliant webdav server.

For those that might find this ticket, one alternative is to build lighttpd without --with-webdav-locks. Of course, that means that files won't be protected by webdav locks. For a number of usage scenarios, this is acceptable, but for others, that behavior is not. This is not a generic solution, of course.

Another possibility is that this issue might be addressed by the lighttpd-git-infinite-locks-regular-files.patch in https://redmine.lighttpd.net/issues/1953

Submitted pull request https://github.com/lighttpd/lighttpd1.4/pull/34 to support Depth: Infinity locks on files.

That should fix this issue in this ticket where Depth header was missing in LOCK request from Microsoft-WebDAV-MiniRedir/6.1.7600. Hopefully Microsoft-WebDAV-MiniRedir was been updated in the meantime to include a Depth header, as immediately prior to the LOCK request, Microsoft-WebDAV-MiniRedir makes a PROPFIND request (in the trace provided further above) and knows whether the target is a file or a directory (webdav collection).