If I try to connect to a secure webdav share (https) using nautilus's 'Connect to Server' option, it fails to connect, giving me an "HTTP Error: Authorization Required" error. If I don't put the username in the initial dialog (and instead wait for it to ask me afterwards) I get the following in my access log: 10.8.0.10 - - [25/May/2010:15:20:09 -0400] "OPTIONS /docrepo HTTP/1.1" 401 401 "-" "gvfs/1.2.3" Then I get the dialog that asks me for my username/password It appears that gvfs is actually sending the unauthenticated request first, then asking, and never sending the authenticated request. (no new entries in the log appear) gnome-base/gvfs-1.2.3 gnome-base/nautilus-2.26.4 net-libs/libsoup-2.28.2 net-libs/libsoup-gnome-2.28.2 Reproducible: Always Steps to Reproduce: 1. Set up a webdav share with the following (for instance) <Location /docrepo> DAV svn SVNPath /home/svn/repos/docrepo SVNAutoversioning on DavGenericLockDB /home/svn/locks/docrepodavlock ModMimeUsePathInfo on AuthType Digest AuthName "Document Repository" AuthDigestDomain "Document Repository" AuthDigestProvider file AuthUserFile /etc/apache2/htpasswd/docs.htdigest AuthDigestAlgorithm MD5 Require valid-user </Location> 2. click Places->Connect to server 3. select Secure WebDAV (HTTPS) 4. enter the server and folder 5. Actual Results: Get a dialog that says: Cannot display location "davs://andy@eeble.net/docs" HTTP Error: Authorization Required and an entry (before I even enter my password) in the apache access logs that says: 10.8.0.10 - - [25/May/2010:15:24:25 -0400] "OPTIONS /docrepo HTTP/1.1" 401 401 "-" "gvfs/1.2.3" Expected Results: A new nautilus window with the webdav share mounted. If I instead switch the apache config to use Basic authentication, it works as expected (albeit a little wonky when you do things like create new folders... it says they don't exist because the order in which nautilus creates/renames then is a little off)
crap. I configured my apache stuff wrong.
(In reply to comment #1) > crap. I configured my apache stuff wrong. > Yep. I was right, I fixed my AuthDigestDomain and it works, though it appears that you have to NOT give it a username in the initial dialog, and instead give botht he username and password in the secondary dialog that comes up.
