Sander Striker suggested that I forward this to [EMAIL PROTECTED]
as a potential "dirwalk/location walk logic" bug. So here goes...
------- Start of forwarded message -------
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Date: 14 Nov 2001 09:17:06 -0600
Message-ID: <[EMAIL PROTECTED]>
Subject: Gack! Weirdo DAV bug.
I have a Subversion repository at /usr/www/repositories/test on my
box. Been using it forever. Until last night, the httpd.conf
directives looked like this:
<Location /repos/test>
DAV svn
SVNPath /usr/www/repositories/test
</Location>
Then, I needed to test something auth-related. So, I copied the
Subversion users auth file from svn.collab.net to my local box, and
copied the directives for using that file from svn.collab.net's
httpd.conf. Now it looks like this:
<Location /repos/test>
DAV svn
SVNPath /usr/www/repositories/test
AuthType Basic
AuthName "Subversion repository"
AuthUserFile /usr/www/svn-user-file
<LimitExcept GET PROPFIND OPTIONS REPORT>
require valid-user
</LimitExcept>
</Location>
Upon doing this, I was able to checkout and commit and such with no
problem. My first commit even appropriate queried me for a password.
However, when I tried to update from the top level of my working copy,
I got this:
apr_error: #20014, src_err 0 : <Error string not specified yet>
The REPORT status was 500, but expected 200.
Checking out Apache's error log, I saw:
[Wed Nov 14 08:56:42 2001] [warn] [client 127.0.0.1] handler
"dav-handler" not found for: /usr/www/docroot/repos
If I reverted my httpd.conf to the non-auth setup, all was well. With
auth, I got the error, every time.
I looks as though somewhere, something is splitting the URL from
http://localhost/repos/test to http://localhost/repos, which maps to
/usr/www/docroot/repos, and of course is NOT a dav-handled thing.
Thinking further, I wondered if this was happening on svn.collab.net
as well, but that I never saw it because I have `trunk' checked out
(trunk's parent dir is still inside the repos). So I checked out
http://svn.collab.net/repos/svn, and tried to update. Same error.
That sucks.
Weird thing is that is only seems to happen when the auth stuff is
present. Hopefully that will help me (or someone else) track this
down.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------- End of forwarded message -------
