The right settings ?

If I try to create a directory, at the root or in a subdirectory, after typing the name of the directory, Nautilus tells me that it can't change the name because the place is not mounted, and I am left with a folder called "New Folder". But If a do a refresh, I see the folder with the right name.

With WebDAV clients that are file system browsers, as opposed to FTP-like browsers, this is sometimes the case since the client does two stages -- creation of a placeholder folder ("new folder", "untitled folder", etc.) and then rename of the folder. I don't have access to Nautilus to test this specifically, but I have seen it in Mac OS X's Finder, for one.

After folder creation, a new term appears in the vocabulary. But if the folder is at the root of the repository, it does not create a new vocabulary. I think this is not a true problem for now, but it can be surprising. I will just tell my users to use dav/myvocabulary.

There does seem to be a problem with vocabulary creation right now -- I'm getting an HTTP 405 myself. I will investigate this.

I have no more file association with programs ! If I have a PNG or a XLS file, my OS does not know anymore with which program to open them.

This again will vary by operating system and client. In the Mac clients that I've been using, the client has its own mapping of what programs to use, separate from the OS. The DAV server is providing a filename extension and a MIME type, so there is nothing more that it can do here.

Some programs cannot open the files on the file server. This is the case with Gimp and Gedit, while OpenOffice succeeds.

See above.

When I upload files, I can see them as new nodes (yeah !). But I do not have a lot of interesting information in the node. Here is how a simple .txt file look like :

Two things to try here:

1) Try creating a node of type 'file' manually through the website, first, to make sure that your File Framework setup is ok.

2) Check out the configuration for the File Framework (/admin/settings/file/configure) for server-side MIME type autodetection. Some clients (browsers and WebDAV clients, both) do not provide the correct MIME info, so Drupal has no way of knowing the file type. If you can get the server-side detection working, you can work around this and your files will no longer be created as nodes with "unrecognized file type".

Hope this helps, and thanks for giving the module a shot.

Regarding the vocabulary creation problem:

After folder creation, a new term appears in the vocabulary. But if the folder is at the root of the repository, it does not create a new vocabulary. I think this is not a true problem for now, but it can be surprising. I will just tell my users to use dav/myvocabulary.

Do you have any other modules enabled that use the DAV API, such as DAV file system? There is currently an issue with creating collections (i.e., folders) at the root level when more than one module is in play.

Hi Justin, and thank you for your answer.

There seem to have some incompatibility with Nautilus. I will try with another file browser, to see which problems I meet. But on my other, plain, DAV server I do not have those problems. Maybe the implementation of DAV differs between HTTP_WebDAV_Server and mod_dav on Apache ?
Right now, it is not working anymore on Nautilus while it was two days ago. But I can still connect with Firefox, so this is weird. I will investigate this.

Is there something I can do regarding MIME types ? On my plain DAV server it works.

Two things to try here:

1) Try creating a node of type 'file' manually through the website, first, to make sure that your File Framework setup is ok.

2) Check out the configuration for the File Framework (/admin/settings/file/configure) for server-side MIME type autodetection.

I tried this. First I tried with a PDF file and it did not work. I went to the File Framework and I saw that there was nothing associated to PDF file format. So I tried again with a simple text file and it worked ! I could see a preview of the .txt file.
In File Framework configuration, I also disabled the Generated (converted) files" option which made all the ( bytes) | view | download | info appear.

Do you have any other modules enabled that use the DAV API, such as DAV file system? There is currently an issue with creating collections (i.e., folders) at the root level when more than one module is in play.
I was so I disabled it (I had no use for it in fact). It worked : it created a new vocabulary when I created a new folder. This is great.

Now I will try to have server side MIME-type detection working. I need some time to test this, I will tell you if it works.

Thank you for your help. Now the main problems seem to be linked to Nautilus compatibility.