Re: Limiting access to only commit messages

On 1/25/06, David Resnick <abunetta@gmail.com> wrote:
> doesn't
> describe what the connection is between Apache access methods and Subversion
> actions.

That's because the mapping of HTTP methods to Subversion actions is
insanely complex. Typically several methods are required to achieve a
single subversion action. You can see a description here, though it's
only a very high-level view:

  http://svn.collab.net/repos/svn/trunk/subversion/libsvn_ra_dav/protocol

From the user's standpoint, then, the only things that exist are

  * blanket read/write control using apache <Limit> or <LimitExcept> directives
  * per-path read/write control using mod_authz_svn

You can *try* telling apache to allow nothing but PROPFIND requests,
and that *might* do what you want, but I'm skeptical it will work.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 25 15:00:51 2006