Bug 807571 - mod_dav_svn: SVNListParentPath and AuthzSVNAccessFile conflict
Summary: mod_dav_svn: SVNListParentPath and AuthzSVNAccessFile conflict
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subversion
Version: 6.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Joe Orton
QA Contact: qe-baseos-daemons
Depends On:
TreeView+ depends on / blocked
Reported: 2012-03-28 08:04 UTC by Petr Sklenar
Modified: 2018-01-22 13:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-03-04 14:03:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Petr Sklenar 2012-03-28 08:04:54 UTC
Description of problem:
directive AuthzSVNAccessFile doesn't work well together with SVNListParentPath on

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
0. there are svn repositories in /var/www/svn/

1. cat /etc/httpd/conf.d/subversion.conf
<Location /example/>
  DAV svn
  SVNParentPath /var/www/svn/
  SVNListParentPath on

  AuthBasicProvider file
  AuthType Basic
  AuthName "Subversion"
  AuthUserFile /etc/httpd/conf/subversion.passwd
  Require valid-user

  Order allow,deny
  Allow from All
  Satisfy Any
  Options Indexes MultiViews IncludesNoExec

  AuthzForceUsernameCase Lower
  AuthzSVNAccessFile /etc/httpd/conf/subversion.authorization


2. cat /etc/httpd/conf/subversion.authorization
* = rw
* = rw
Actual results:
you need to specify '<Location /example/>' to be able list parent repositories.
'<Location /example>' doesn't allow you to list collection of repositories.

Expected results:
'<Location /example>' is enough and you can see collection of repositories on http://<hostname>/example

Which works well when you comment out AuthzSVNAccessFile line

Additional info:

There is common work around for authz and SVNListParentPath issue
RedirectMatch ^(/example)$ $1/

Comment 2 RHEL Program Management 2012-05-03 05:29:21 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Note You need to log in before you can comment on or make changes to this bug.