The DavFSv2 client

Connecting on the command line

Provided it is installed and everything
Enter : mount -t davfs http://urltoyourwebdavserver mymountpoint

Implementor notes

DavFS seems to be the best (popular) WebDAV implementation. DavFS requires A Class 2 server, otherwise it will go into read-only mode. It is possible to go into a read-write mode without a Class 2 server, by specifying the nolocks option.

By default DavFSv2 will do lots of buffering and caching. This means that even though a user has written to a file locally, it can take a while before the changes actually show up on the server. This can be quite confusing when working in teams.

Protocol Details

The user-agent I got was davfs2/1.1.2 neon/0.26.2
The client makes use of lock-null requests. This basically means it will lock non-existant resource before it starts writing them. Very annoying!

Properties

DavFSv2 asks for the following properties from the DAV: namespace

displayname
getetag
getcontentlength
creationdate
getlastmodified
resourcetype

And from the http://apache.org/dav/props/ xml namespace

executable

Comment by moo...@wwwendt.de, Jan 9, 2010

Hi,

> The client makes use of lock-null requests. This basically means it will lock non-existant resource before it starts writing them.

that's OK by the current RFC: http://www.webdav.org/specs/rfc4918.html#lock-unmapped-urls

regards Martin

Comment by project member evert...@gmail.com, Jan 9, 2010

True =) This note was added because I felt it was an interesting difference between DavFS and most other clients.

► Sign in to add a comment