[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Apache setup, user access

From: Dale Hirt <dale_at_sbcltd.com>
Date: 2005-09-17 18:13:58 CEST

Personally, I would check out the documentation on mod_authz_svn instead of using Limit or LimitExcept.
http://svnbook.red-bean.com/en/1.1/ch06s04.html#svn-ch-6-sect-4.4 then scroll down to "Per-Directory Access Control".


From: Dave Pawson [mailto:dave.pawson@gmail.com]
Sent: Sat 9/17/2005 6:55 AM
To: users@subversion.tigris.org
Subject: Apache setup, user access

I'm getting confused with <Limit ...> and <LimitExcept ...>


The purpose of the <Limit> directive is to restrict the effect of the
access controls to the nominated HTTP methods.

So if I have
<Limit POST PUT >
Require valid-user

Then the users in the passwd file will be able to PUT and POST

With LimitExcept, I'm less clear.
<LimitExcept> and </LimitExcept> are used to enclose a group of access
control directives which will then apply to any HTTP access method not
listed in the argument

So <LimitExept GET>
Require valid-user

will ... what? require a recognised user for everything except GET?

I'm trying to set up a Subversion repository which has
password protected read access, and no other access.

Any suggestions which method is appropriate please?


Dave Pawson
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 17 18:18:00 2005

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.