You've definitely given me enough to work off here, thanks!
Benjamin Ortega
-Original Message-
From: Mark Phippard [mailto:markp...@gmail.com]
Sent: Monday, January 03, 2011 9:18 AM
To: Ortega, Benjamin
Cc: users@subversion.apache.org
Subject: Re: On commit attempt, Server sent unexpe
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
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?
Benjamin Ortega
-Original Message-
From: benjamin.ort...@wellsfargo.com [mailto:benjamin.ort...@wellsfargo.com]
Sent: Mo
The /*/*/*/ in the path is to compensate for the temporary location
/!svn/ver//. This works without the svnauthz file in place.
Is there an internal user that the subversion server utilizes to perform the
checkout of the last-committed-revision of the file prior to the put? That
seems to be w
I'm trying to integrate a SVN Authz authorization file with apache
configuration files to provide a solution for not just directory level
restrictions, but also file level restrictions. It's my understanding that the
SVN Authorization file is not capable of handling file-specific restrictions,
That can't be right, since it works perfectly when I use the authz file by
itself. When I add that apache location in, everything except the file that is
indicated in that location works exactly as expected with the authz file in the
order I have it.
Benjamin Ortega
--
I'm trying to integrate a SVN Authz authorization file with apache
configuration files to provide a solution for not just directory level
restrictions, but also file level restrictions. It's my understanding that the
SVN Authorization file is not capable of handling file-specific restrictions,
