The OS X finder uses a very large range of webdav features, including the only example of chunked PUTs. The only server i've found that works well is Apache mod_dav. We use it heavily against Leopard and Maven.
Assid from lighttpd there is also a webdav module for nginx, but it doesn't work at all for properties, and can't do chunked PUTs.
Apple have also released their calender server, which uses CalDAV extentions, so it should work against the finder. I haven't used that product, so can't vouch for it as a general webdav server.
When looking for compatible options you should check out the following projects
Just today was I tracking down problem with Mac uploads. Turned out that Mac not only uses chunked encoding when doing PUT (all other clients I checked send Content-Length instead), but it also specifies "Transfer-Encoding: Chunked" with capital C, instead of "chunked", and mod_proxy doesn't like that.
The OS X finder uses a very large range of webdav features, including the only example of chunked PUTs. The only server i've found that works well is Apache mod_dav. We use it heavily against Leopard and Maven.
Assid from lighttpd there is also a webdav module for nginx, but it doesn't work at all for properties, and can't do chunked PUTs.
Apple have also released their calender server, which uses CalDAV extentions, so it should work against the finder. I haven't used that product, so can't vouch for it as a general webdav server.
When looking for compatible options you should check out the following projects
Just today was I tracking down problem with Mac uploads. Turned out that Mac not only uses chunked encoding when doing PUT (all other clients I checked send Content-Length instead), but it also specifies "Transfer-Encoding: Chunked" with capital C, instead of "chunked", and mod_proxy doesn't like that.
Seems that lighthttpd also doesn't like chunked transfer encodings on PUTs.
We use Tomcat + Apache Jackrabbit Webdav library on server side, and Mac Finder works fine with it.