* Ben Reser <ben@reser.org> [2004-08-23 10:49]:
> > Use the exact same authorization mechanism. For example, something like this:
> >
> > # Subversion repository
> > <Location /svn>
> > DAV svn
> > SVNPath /path/to/repos
> > AuthType Basic
> > AuthName "Subversion Repository"
> > AuthUserFile /usr/local/apache2/conf/svn-auth
> > Require valid-user
> > AuthzSVNAccessFile /usr/local/apache2/conf/svn-access
> > </Location>
> >
> > # ViewSVN
> > ScriptAlias /viewsvn /path/to/viewcvs.cgi
> > <Location /viewsvn>
> > SVNPath /path/to/repos
> > AuthType Basic
> > AuthName "ViewSVN"
> > AuthUserFile /usr/local/apache2/conf/svn-auth
> > Require valid-user
> > AuthzSVNAccessFile /usr/local/apache2/conf/svn-access
> > </Location>
>
> Huh? Will that actually work? mod_authz_svn's primary purpose is to
> decode the special URLs we use into a fashion that can do path based
> authorization.
Works for me... because it's in a <Location> block, I think the path being
accessed looks exactly the same to mod_authz_svn whether it's being accessed
via /svn or /viewsvn (i.e. both http://example.com/svn/foo and
http://example.com/viewsvn/foo require authorization to access /foo in the
repository at /path/to/repos).
--
Michael W. Thelen
No amount of genius can overcome a preoccupation with detail.
-- Levy's Eighth Law
Received on Mon Aug 23 23:22:02 2004