I'm having trouble to create/access a Subversion repo in a WebDAV
directory hosted at my web hosting company (DreamHost). I'm using svn and
RapidSVN on Windows XP SP2.
When I try to access the WebDAV repo using svn using an http:// URL, I get
a "400 Bad Request" error:
C:\temp>svn co --username username --password password http://www.example.co
svn: PROPFIND request failed on '/webdav/svn'
svn: PROPFIND of '/webdav/svn': 400 Bad Request (http://www.example.com)
When I look in Apache's access.log, I see:
18.104.22.168 - - [21/May/2005:10:39:21 -0700] "PROPFIND /webdav/svn HTTP/1.1" 40
1 - "-" "SVN/1.1.4 (r13838) neon/0.24.7"
When I look in Apache's error.log, I see:
[Sat May 21 10:39:56 2005] [error] [client 22.214.171.124] File does not exist:
Other reports of "400 Bad Request" were commonly proxy problems, but I'm
not using a proxy. Plus, I can successfully access this same WebDAV
directory using Windows XP's built-in WebDAV support. I can also
successfully access another repo (on someone else's server) using the
IMPORTANT NOTE! To get Windows XP's built-in WebDAV support to work, I did
have to edit the Windows Registry to re-enable HTTP BasicAuth. Apparently,
Windows 2000 and XP supported BasicAuth by default, but Windows XP SP2
(which I'm using) disabled BasicAuth (for obvious security reasons).
Could svn be trying to use BasicAuth and failing? That might explain why
Apache's error.log reports that Apache was trying to find
"failed_auth.html" to return to the client. If svn was actually sending a
bad request, I would expect to see an error in error.log that Apache was
trying to find "bad_request.html". Or if a proxy was blocking svn's
PROPFIND request, then I would not expect to see ANY mention of my svn
request in Apache's access.log or error.log.
So after all this explanation, I suspect my problem is that svn is trying
to use HTTP BasicAuth and failing because I'm using Windows XP SP2. How
can I make svn using DigestAuth or something else?
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat May 21 20:13:28 2005