Robin Becker wrote:
> What Apache config do I use for
> http://host/svn/public world readonly
> https://host/svn/public developer writable
> http://host/svn/private invisible
> https://host/svn/private developer readable/writable
> I'm using the following and it fails to allow a valid login.
> in httpd.conf
> <Location /svn/public>
> DAV svn
> SVNPath /svn/public
> <LimitExcept GET PROPFIND OPTIONS REPORT>
> Order deny,allow
> deny from all
> in the ssl.conf
> <Location /svn>
> DAV svn
> SVNParentPath /svn
> AuthzSVNAccessFile /HTTPD/etc/svn_access
> Satisfy Any
> AuthType Basic
> AuthName "Subversion Repository"
> AuthUserFile /HTTPD/etc/passwd
> Require valid-user
Probably your biggest problem here is the fact that ssl.conf isn't
really a separate configuration file that Apache uses for only https.
Rather, it gets wholly included into httpd.conf at startup. Look for a
line like "Include conf.d/*.conf" in httpd.conf; in effect, that line
gets replaced with the contents of all .conf files in the conf.d
directory. Some Linux distros do this to make managing httpd-specific
packages easier (they can just create the .conf files they need instead
of editing the monolithic httpd.conf), but I always find it annoying and
just make one httpd.conf with all my settings, and remove the "Include"
So, your general "Location /svn" block is getting wiped out by the more
specific "Location /svn/public" block for ALL requests, whether http or
https. I believe the way to achieve what you want is to create two
separate <VirtualHost> blocks. They can both use the same IP, but
different ports (80 and 443 for http and https, respectively).
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Jun 9 23:17:51 2004