Like a number of other people I'm having problems getting WebDAV to work in Vista (retail Ultimate). I've been troubleshooting this for a couple of weeks and I can get it to work, but not consistently.

Server: Linux with Apache 1.3 (basic authentication with SSL)
Client: Vista Ultimate with Microsoft-WebDAV-MiniRedir 6.0.6000

URL format: [URL]https://[/URL][host]/dav/[username].

Note that authenticating and mounting the web share is the problem. When it mounts correctly everything else runs smoothly until the system is rebooted or the mounted share window is closed.

Also note that I have already overcome the known problems (OPTIONS on root, basic auth on non-SSL, etc).

Mount Method 1: Hyperlink (#default#AnchorClick behavior)

This is my desired method. It consistently works when launching a brand new connection (when Window's doesn't have the login information cached), but not subsequent launches. I just tried opening a share from hyperlink 6 times in a row and it: worked, worked, failed, failed, worked, and failed.

Mount Method 2: Add Network Location

This consistently fails unless I first successfully mount the hyperlink way..

Mount Method 3: Map a Drive

This consistently works when setting up a mapping, but if the user checks the box to reconnect at login, that part fails. The user is forced to disconnect the drive and remap it. The problem here seems to be authentication. On initial mapping the auth string sent to the server is host\user:pass. After rebooting the reconnect sends host\user: (password is missing). The mapped drive has a big red X on it and double clicking to open gives the error "The operation being requested was not performed because the user has not been authenticated."

Any extra info or tricks to try would be great. . .

I'm using http (with basic auth registry "hack") and tcpflow to watch requests and responses. The server's responses are valid and consistent. I'd be happy to provide tcpflow logs or a URL with user/pass for to test with.

Another problem to point out with Microsoft-WebDAV-MiniRedir/6.0.6000. After renaming a file (which includes after creating a new folder and giving it a name) a series of bad PROPFIND requests are sent to the server. If these aren't handeled correctly MiniRedir will think the rename failed and not update the GUI.

> PROPFIND /dav/davtest/myfolder
< HTTP/1.1 207 Multi-Status

> MOVE /dav/davtest/myfolder HTTP/1.1
< HTTP/1.1 201 Created

> PROPFIND /dav//davtest/renamedfolder HTTP/1.1
< HTTP/1.1 401 Authorization Required

Note the double // in the PROPFIND path. It does this 4 times before giving up. If you're reading this and having problems renaming or creating new folders you have to be able to handle the //. I threw in regular expression replace to switch the // to /.