Re: path-based access control issues

Just spotted the difference between the docs linked below and what I was
doing.

[reponame:/path/to/dir] works

[reponame:/path/to/dir/] doesn't

So: adding a trailing slash to the path causes access denial.

Thanks for listening, hope this helps someone else ...

【ツ】

On Wed, Nov 25, 2009 at 12:32 AM, chris burgess <xurizaemon_at_gmail.com>wrote:

> I've been accessing Subversion fine by both HTTP (apache2) and SSH until
> today, when I had a need to restrict a user to a specific directory. I can't
> work out how to configure SVN to do this and have it work. I'm basing my
> config on the instructions at
> http://svnbook.red-bean.com/en/1.4/svn.serverconfig.pathbasedauthz.html
>
> If I use a path directive like [reponame:/] it works as expected. If I use
> a path directive like [/] it works as expected.
>
> But if I use a path directive like [reponame:/path/to/dir/] then it returns
> a 403 against the OPTIONS request when auth details are provided. I can
> reliably reproduce the issue by removing any path elements beyond a simple
> [reponame:/].
>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2424029

Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-11-25 01:15:40 CET