[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Unexpected behaviour with SVNPath/SVNParentPath mixture

From: Ryan Schmidt <subversion-2011a_at_ryandesign.com>
Date: Thu, 24 Mar 2011 20:24:55 -0500

On Mar 24, 2011, at 10:12, <Ullrich.Jans_at_elektrobit.com> <Ullrich.Jans_at_elektrobit.com> wrote:

> we're trying to set up the following config:
>
> http://svnserver/svn/parentpathtest
> |- repo1
> |- repo2
> \- repo3
>
> The internal users of the project are supposed to be able to access all three repositories, while a bunch of external users are supposed to be able to access only repo2. We've been trying to achieve this with the following config:
>
> <Location /svn/parentpathtest>
> DAV svn
> SVNParentPath /subversion/parentpathtest
> AuthType Basic
> AuthName "Repository /svn/parentpathtest"
> Require ldap-group CN=pr_parent,OU=Groups,DC=sub,DC=example,DC=com
> </Location>
>
> <Location /svn/parentpathtest/repo2>
> DAV svn
> SVNPath /subversion/parentpathtest/repo2
> AuthType Basic
> AuthName "Repository /svn/parentpathtest/repo2"
> Require ldap-group CN=pr_parent_ext,OU=Groups,DC=sub,DC=example,DC=com
> </Location>

You will either want a single Location block containing an SVNParentPath directive, or multiple Location blocks each with an SVNPath directive. Not both.
Received on 2011-03-25 02:25:29 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.