RE: On commit attempt, Server sent unexpected return value (403 Forbidden) in response to CHECKOUT

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? Like:

[repos:/folder/structure/*/RestrictedFile]
To allow for one entry restricting access to the same file in multiple branches, etc? Just for ease of admin is all.

Benjamin Ortega

-----Original Message-----
From: Mark Phippard [mailto:markphip_at_gmail.com]
Sent: Monday, January 03, 2011 8:59 AM
To: Ortega, Benjamin
Cc: users_at_subversion.apache.org
Subject: Re: On commit attempt, Server sent unexpected return value (403 Forbidden) in response to CHECKOUT

On Mon, Jan 3, 2011 at 9:55 AM, <Benjamin.Ortega_at_wellsfargo.com> wrote:
> I suppose another fundamental question in all this -- Is there any other way to provide file level restrictions
> while using the svn authz file for authorization?

Can you explain why you cannot just add a rule to the file like this:

[repos:/folder/structure/RestrictedFile]
* =
my_username = rw

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/