From: Marco Cavalieri <marcocav@io...> - 2008-03-10 22:34:43
I'm trying to set up a Dav-enabled server using yaws 1.75 and
Erlang/OTP R11B on Ubuntu 7.10.
After starting yaws, I can read the contents of the site using a browser.
However, it is not possible to connect to the site with a WebDav client.
Using cadaver gives the following error:
$ cadaver http://localhost:9081/
Authentication required for foobar on server `localhost':
Could not access / (not WebDAV-enabled?):
Did not find a collection resource.
Connection to `localhost' closed.
If I tell cadaver to ignore errors (-t option) I can see the directory
contents, but any attempt
to 'put' a new file results in cadaver displaying a 100% progress bar,
then hanging for about
30 sec and finally failing with '409 Conflict'.
Could this behaviour depend on some configuration error on my side?
The server configuration is:
port = 9081
listen = 0.0.0.0
docroot = ./dav
dir_listings = true
dav = true
realm = foobar
dir = /
user = foo:bar
user = baz:bar
Any help would be appreciated.
Claes Wikström wrote:
> Marco Cavalieri wrote:
>> <server localhost>
>> port = 9081
>> listen = 0.0.0.0
>> docroot = ./dav
>> dir_listings = true
>> dav = true
>> realm = foobar
>> dir = /
>> user = foo:bar
>> user = baz:bar
> The yaws dav impl. is pretty lame. I'm not even sure if
> yaws dav + auth works. Maybe some of the dav authors could comment.
The DAV support in Yaws is in very poor shape and is in need
of some serious caretaking. Any (care)takers... ?