That was my concern as well and the following did work without prompting
for a password. I did realize though that we had a path that was not
supposed to be publicly readable. In playing with how to deal with that
I found the following works as well. You get 403s for write operations
and read o
2010/3/23 Eric Dalquist :
> We would like to have a version of our SVN repository available read-only
> over HTTP.
I have not tried, but I think you can do the following:
...
Order Deny,Allow
Deny from all
If you are providing access both by HTTP and HTTPS it might be a bad
idea to
Do you want people to be able to fetch pages from Subversion over a
web page? Or do you want people to be able to checkout code, but not
be able to check in changes?
If you want your source and all versions accessible over a web
browser, you might want to look at Sventon (which is free), ViewCS, o
Thanks for the tip. I switched to this approach which gives us the 401
we want.
On 03/23/2010 09:44 AM, Rob van Oostrum wrote:
My guess is it doesn't like that you have the Require without
Authentication configured. The way I usually do this is have the
anonymous read / authenticated & authori
My guess is it doesn't like that you have the Require without Authentication
configured. The way I usually do this is have the anonymous read /
authenticated & authorized write construct (see manual), and give the HTTP
host its own access file where you set * = r for [/], so authorization for
write
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
