> I did some more experimentation and found that by adding a trailing
> slash to the <Location> path helps. In your case above, change it to
> <Location /repositories/>. After adding the trailing slash, I can see
> the repository collection if I put the trailing slash on the request
> URL. In my case, http://svntest/svn/; leaving off the trailing slash
> still gives the access forbidden error.
Excellent, that works. I had kept my settings identical as much as
possible to what was working for my existing Subversion server. It
didn't occur to me that the problem might be solvable by tweaking that
configuration. Thanks.
> It seems the problem may have something to do with the way the Authz
> module parses the repository path.
I checked with Davide Bianchi (I think he's the top poster to the apache
lists :D) who works in my team as to whether he could think of other
consequences of appending this slash and came away with no issues I need
to consider so that's good. My testing so far shows that Subversion
operations continue to work as before. I imagine the only possible
change due to appending the slash is that without it Apache could
theoretically attempt to serve a file called repositories instead of a
directory should that file exist.
Perhaps mod_authz_svn is considering the path without the trailing slash
to mean a file and not a directory which caused the problem? Sounds to
me like mod_authz_svn in that case is not broken, rather my Apache
configuration was.
Once again, thanks.
X
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 6 14:59:29 2006