You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ian Fasel <ia...@gmail.com> on 2004/11/02 03:11:21 UTC

per-directory control fails with SVNParentPath

Hi,

I've configured apache2 to access svn (and using ssl to boot).  It
works correctly when my ssl.conf has this
  SVNPath /usr/local/svn/project
in the Location block and then in svnserve.conf I use this:
  [/]
  sarah = r
  [/Labeling]
  fred = r
In other words, it correctly allows sarah to access everything in the
repository called project, and only allows fred to access
project/Labeling.

However, if I change from SVNPath to
   SVNParentPath /usr/local/svn
in the Location block and then change the svnserve.conf to have this:
  [project:/]
  sarah = r
  [project:/Labeling]
  fred = r

I thought this would have the same behavior, but instead I can't
access anything as anybody (i.e., access is always denied).
Interestingly, if I add this to svnserve.conf
  [/]
  sarah=r
While still using SVNParentPath, then sarah is now allowed to access
*all* of the svn projects located in /usr/local/svn, e.g.,
  /usr/local/svn/project2
as well.

Any ideas on what I'm doing wrong?

Here's my configuration
Mac OS X Server 10.3.5
using fink to install version 1.0.9-11 of
    svn-ssl
    libapache2-ssl-mod-svn 
and version 2.0.50-10 of
    libapache2-ssl
and all of the associated libraries, etc.

Thanks for any help on this!
-Ian Fasel

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org