Actually I’m reporting the experience of two years ago, so something could be changed.
So, this is how I made davfs works on Debian Sarge.
Since 0.2.8 there was debian package for sarge and actually there’s a binary installation that I’ve not tested. If you are using etch (or later) distribution, davfs should come with repositories. So installing should be something simple like
#dpkg -i <pagkage>
#aptitude install davfs2
The documentation said (remember I tested it two years ago), that it should be possible to specify and outgoing proxy in ~/.davfs2/davfs2.conf but it didn’t work for me. It seemed that only the /etc/davfs2/davfs2.conf file was ridden.
Inside this last file specify the proxy in the form
If you need to specify an authentication you can use the secrets file that must have the permission to 600. In this file you will specify both proxy and webdav authentication.
proxy.domain.com user password
http://davserver/path user password
then in order to mount the remote file system, in /etc/fstab specify
http://davserver/path mountpoint davfs user,noauto,rw 0 0
Now from root it is possible to mount the remote server
If you have a pc that is shared by many users, and while the authentication by the configuration in the home directory didn’t work, it is possible to remove them from the secrets file and modify the /etc/fstab as following
http://davserver/path mountpoint davfs user,noauto,rw,askauth 0 0
In this way each person who will mount the remote file system, will be required to input user and password.
In order to allow all allowed user to mount the file system (and not only root), you need to give the 4755 permissions to the /usr/lib/mount.davfs-2.6 file