subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Rodgers <christopher.rodg...@cardiov.ox.ac.uk>
Subject Query about warnings: mod_dav_svn: nested Location '/repos/reponame' hinders access to '' in SVNPath Location '/repos/reponame'
Date Thu, 05 Oct 2017 10:31:37 GMT
Dear Subversion team,

I run subversion on a Fedora 26 machine, with Apache 2.4.27 and
Subversion mod_dav_svn 1.9.7 installed from the Fedora repositories.

I see lots of errors like this in my httpd error_log:

> [Thu Oct 05 10:53:19.131284 2017] [:warn] [pid 30014] mod_dav_svn:
> nested Location '/repos/reponame' hinders access to '' in SVNPath
> Location '/repos/reponame'
Here is the section for this repository in
/etc/httpd/conf.d/subversion.conf:

> <Location /repos/reponame>
>    DAV svn
>    SVNPath /srv/svn/repos/reponame
>    SVNIndexXSLT "/repos-web/view/repos-reponame.xsl"
>
>    # Include per-directory access control policy
>    AuthzSVNAccessFile /srv/svn/user_access/reponame_authz
>
>       # Require SSL connection for password protection.
>       SSLRequireSSL
>
>       AuthType Basic
>       AuthName "Authorization Realm"
>       AuthUserFile /srv/svn/user_access/reponame_passwd
>       Require valid-user
> </Location>

There are other equivalent <Location /repos/othername> blocks too.

How can I suppress this warning? / Does it matter?

Things I previously tried:

1. Per https://groups.google.com/forum/#!topic/subversion_users/kQNOHEYjjvs

I grepped all files in /etc/httpd to check. I do not have any nested
Location blocks in my config.

2. Again per
https://groups.google.com/forum/#!topic/subversion_users/kQNOHEYjjvs

I adjusted the Location block to <Location /repos/reponame/>

and SVNPath /srv/svn/repos/reponame to SVNPath /srv/svn/repos/reponame/

(i.e. adding a trailing slash).

But this did not remove the warning, AND it meant that a svn clients now
show an error accessing the repository root:

> $ svn ls 'https://hostname/repos/reponame'
> svn: E175002: Unable to connect to a repository at URL
> 'https://hostname/repos/reponame'
> svn: E175002: The OPTIONS request returned invalid XML in the
> response: XML parse error at line 1: no element found
> (https://hostname/repos/reponame)
>
> and
>
> $ svn ls
> 'https://cardiosvn.fmrib.ox.ac.uk/repos/crodgers/'                                                      
>  
> svn: E175002: Unable to connect to a repository at URL
> 'https://hostname/repos/reponame'
> svn: E175002: The OPTIONS request returned invalid XML in the
> response: XML parse error at line 1: no element found
> (https://hostname/repos/reponame)
>
>
Note that the two svn ls commands both send a URL to the server (seen in
the access_log) WITHOUT the trailing slash.


Using Chrome web browser, I see a 404 error at
https://hostname/repos/reponame (correctly I think - there is no such
file in the httpd web root folder) and I see the repository listing at
https://hostname/repos/reponame/


Using TortoiseSVN's repository browser FAILS with this setup with an XML
error like the command line.


svn ls, Chrome, and TortoiseSVN's repository browser can access folders
within the repository OK, e.g. svn ls
'https://hostname/repos/reponame/dir1' or svn ls
'https://hostname/repos/reponame/dir1/' are both fine.

Best wishes,

Chris.


Mime
View raw message