I am working to upgrade my servers to SVN 1.7.8 and just ran into a
weird issue. If I look at the repository via the web, it shows up as
empty. At first I thought it was something with the repos-web
stylesheet I'm using, but looking at the page source I see this:
<svn version="1.7.8 (r1419691)"
href="http://subversion.apache.org/";>
<index rev="119763" path="/" base="foobar">
</index>
</svn>
But if I use that exact same URL on the command line, it works as I expect:
$ svn ls https://adc4110316.us.oracle.com/svn/foobar/
README
branches/
tags/
trunk/
Furthermore my WebSVN pages show the repository correctly, so this isn't
a show-stopper. If I access a subdirectory it works correctly via all
three methods.
FYI, here's my apache config (slightly redacted) for that repository
(this is the exact same config I'm using for my 1.6 servers):
<Location /svn/foobar>
DAV svn
SVNPath /scm/svn/repos/foobar
SVNIndexXSLT "/repos-web/view/repos.xsl"
SVNPathAuthz on
AuthzSVNAccessFile /scm/svn/repos/foobar/conf/authz
AuthType Basic
AuthLDAPURL ldap://[...]
AuthzLDAPAuthoritative On
Require valid-user
Satisfy Any
</Location>
The authz file contains only "[/]" and "$authenticated = r", so I
certainly should be able to read it.
After a bit more testing, I think I figured it out. When I access the
top of the repository, it does not request authentication via the web
(and, thus, gives me an empty page since anonymous access is not
permitted), but it does request authentication via the svn client and
websvn. But if I access a subdirectory, it requests authentication in
all three cases and works as expected. However, my SVN 1.6 server will
request authentication in all cases. So this seems to be a change in
1.7, is it a bug or something that changed in 1.7 and requires config
file changes?
++thanks,
trent...
