However I am unable to mount this same folder. I think I miss something in the command line.
Here are the following attempts:
# mount.davfs http://myserver:8080/cocoon/webdav/ /mnt/dav
Could not connect to `myserver' on port 8080:
Could not connect to server: Connection refused
# mount.davfs http://myserver/cocoon/webdav/ /mnt/dav -o proxy=http-proxy:8080
Could not resolve hostname `http-proxy': Host not foundWebDAV Server error
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Connection refused generally means that there is no program listening on that port.
The first command line looks correct. Maybe you have a typo in the server name?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have compiled dafs-2.0.2.2 from source with a 2.4.18-19.8.0 kernel.
If do
mount.davfs http://test.webdav.org/dav /mnt/dav/
it works fine: i can read and write.
On the other hand I have webdav server that listen on port 8080. The directory I try to mount is world readable, writable and updatable.
I try a webdav client like OpenOffice I just do:
File > Open > http://my-server:8080/cocoon/webdav/test3/
it works fine. I can read, edit and add content in http://my-server:8080/cocoon/webdav/test3/.
However I am unable to mount this same folder. I think I miss something in the command line.
Here are the following attempts:
# mount.davfs http://myserver:8080/cocoon/webdav/ /mnt/dav
Could not connect to `myserver' on port 8080:
Could not connect to server: Connection refused
# mount.davfs http://myserver/cocoon/webdav/ -o proxy=http-proxy:8080 /mnt/dav
Mount point is not an absolute directory
# mount.davfs -o proxy=http-proxy:8080 http://myserver/cocoon/webdav/ /mnt/dav
Mount point is not an absolute directory
# mount.davfs http://myserver/cocoon/webdav/ /mnt/dav -o proxy=http-proxy:8080
Could not resolve hostname `http-proxy': Host not foundWebDAV Server error
Connection refused generally means that there is no program listening on that port.
The first command line looks correct. Maybe you have a typo in the server name?