Date: Mon, 04 Dec 2000 00:40:59 -0800
From: John Grant
Message-id: <20001204004059.A6675@primenet.com>
Subject: Apache 1.3 config change
I just spent a few whiles chasing my tail over an apache configuration
gremlin. I think I figured out what the problem is, or at least a fix,
and thought I'd post this note in the hopes of saving someone else some
grief. I mention it here because I think I saw someone posting here
about the same/related problem a while back. (Maybe come nice rpm
compiler at SuSE could check the apache.rpm and make any necessary
changes to the config files therein to clarify the situation too. :)
The problem is that in the httpd.conf file are the following lines:
-=-=-=-
<p><Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
[...]
UserDir public_html
#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
#
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# </Limit>
# <Limit PUT DELETE PATCH PROPPATCH MKCOL COPY MOVE LOCK UNLOCK>
# Order deny,allow
# Deny from all
# </Limit>
#</Directory>
-=-=-=-
<p>This example is misleading. It seems that sometime between the time
this example was added to the config file and the 1.3.4 version of
apache that I'm using came out the processing of the <Directory>
directive seems to have changed such that that second section doesn't
work. If you uncomment the above directives for the public_html
directory(s) apache processes them with no error, but they don't seem to
be applied. Not the way you would expect according to the comments
anyways.
To make things work you could try simply changing,
[...]
</Directory>
<p>in the example above to,
<p>
[...]
</DirectoryMatch>
<p>.. and you should be in business. At least, that's how I got it
working on one of my systems here.
Hope this helps someone!
<p> -John
