Re: On commit attempt, Server sent unexpected return value (403 Forbidden) in response to CHECKOUT
From: Stephen Connolly <stephen.alan.connolly_at_gmail.com>
Date: Mon, 3 Jan 2011 19:18:29 +0000
a post-commit hook or a crontab coils update the file to keep the security
- Stephen
--- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2011 15:18, "Mark Phippard" <markphip_at_gmail.com> wrote: > On Mon, Jan 3, 2011 at 10:13 AM, <Benjamin.Ortega_at_wellsfargo.com> wrote: >> Wow...for some reason I was under the impression that file level restrictions didn't work...I really don't know why, but there it is. >> >> I don't suppose there's a way to use wild cards in the path as well? > > Wild-cards are not supported in authz. > > If you only needed this to protect writes, then you can do it with a > pre-commit hook. The SVN repository contains svnperms.py which can do > this: > > http://svn.apache.org/repos/asf/subversion/trunk/tools/hook-scripts/ > > However, if you need to protect read access, you cannot do it via a > hook and the Subversion authz module does not support wildcards. > > > -- > Thanks > > Mark Phippard > http://markphip.blogspot.com/Received on 2011-01-03 20:19:08 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.