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

Re: mod_dav_svn: apache authentication

From: Robert Spier <rspier_at_pobox.com>
Date: 2003-05-27 19:55:11 CEST

> | I've hunted through the archives and the documentation, and I've come
> | to the unhappy conclusion that when using apache (mod_dav_svn), the
> | only way to selectively control write access is with a pre-commit
> | hook.
> There is some information in the SVN book about how to make the Apache HTTP
> server require authorization for write-access while providing world
> read-access.
> http://svnbook.red-bean.com/book.html#svn-ch-5-sect-4.1
> Read under "Permissions, Authentication, and Authorization".

Mukund,

    As I mentioned in my original message, the chapter in the book
    doesn't deal with selective permissions. It allows
    whole-repository commits (or not.)

From the book:

<Location /svn>
  DAV svn
  SVNParentPath /usr/local/svn
  AuthType Basic
  AuthName "Subversion repository"
  AuthUserFile /path/to/users/file
  <LimitExcept GET PROPFIND OPTIONS REPORT>
    Require valid-user
  </LimitExcept>
</Location>

  But what I want: (trimmed)

<Location /svn/project/trunk>
 ...
  <LimitExcept GET PROPFIND OPTIONS REPORT>
    Require valid-user
  </LimitExcept>
</Location>

  does not work, because SVN performs write operations using URL's
  like this:

  /svn/!svn/act/90790d4d-32be-0310-9aa5-d593d764d6b9

  which obviously doesn't match the /svn/project/trunk location.

-R

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 27 19:56:29 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.