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

How do SVNPath and SVNParentPath for mod_authz_svn determine the repository name?

From: Ximon Eighteen <ximon.eighteen_at_int.greenpeace.org>
Date: 2005-09-15 23:16:28 CEST

Hi all,

Strange observation:

If my apache config has this:
   <Location /viewcvs/viewcvs.py/ctk>
     SVNPath /cluster_b/data/svn-repositories/ctk
     AuthzSVNAccessFile /cluster_b/system/etc/svn/web_auth.conf

The permissions controlling access will be determined by the [ctk:/] block in
my web_auth.conf file.

If I change SVNPath to this:

     SVNParentPath /cluster_b/data/svn-repositories

all is still well.

However, if I do this:-

  <Location ~ "/viewcvs/viewcvs.py/.+">
     SVNParentPath /cluster_b/data/svn-repositories

The block that matches in web_auth.conf must now look like this:-


Am I doing something wrong?
Is this a bug with mod_authz_svn?
Is this something I don't understand about how Location ~ (otherwise known as
LocationMatch) works?

This isn't stopping my doing anything, but does lead to a messier
configuration file. The reason is that I need /viewcvs/viewcvs.py/ to be
readable to all without an auth prompt and I can achieve this either the first
way or the third way, but the second way causes a prompt (as I'd expect) on
the top URL (/viewcvs/viewcvs.py/) when I only want prompts below that.

The first way I end up with multiple Location blocks for each
/viewcvs/viewcvs.py/repos, each using SVNPath. This works.

The third way I end up with a single Location ~ block but have to define my
permissions twice in my web_auth.conf file, once for the DAV access in
[repos:/] form, and once for ViewCVS access in [viewcvs:/viewcvs.py/repos] form.

Your thoughts appreciated!


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 15 23:19:45 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.