We recently upgrade from 1.5.4 to 1.7.2 and saw a change in behavior
when it comes to filtering content for anonymous versus authenticated
access. The problem appears to be that even though a user has read
access to a specific folder svn commands such as list and checkout
ignore that folder if
uding anon.
[/]
* = r
# Restrict 'read/write' on infrastructure to infrastructure group only
[/infrastructure]
* =
On 3/23/10 3:58 PM, Konstantin Kolinko wrote:
2010/3/23 Eric Dalquist:
We would like to have a version of our SVN repository available read-only
over HTTP.
I h
cated & authorized write construct (see
manual), and give the HTTP host its own access file where you set * =
r for [/], so authorization for write access will always fail.
R.
On Tue, Mar 23, 2010 at 3:39 PM, Eric Dalquist
mailto:eric.dalqu...@doit.wisc.edu>> wrote:
We would like to ha
We would like to have a version of our SVN repository available
read-only over HTTP.
I currently have it setup using:
DAV svn
SVNPath /jasig/svn/jasig
Require valid-user
Which works but I get 500 errors instead of a 401 or 403 like I'd expect:
commit -m "NOJIR
