The following reply was made to PR general/2827; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]>
To: heddy Boubaker <[EMAIL PROTECTED]>
Cc: Apache bugs database <[EMAIL PROTECTED]>
Subject: Re: general/2827: srv fail to read .htaccess on mounted home dirs
Date: Wed, 12 Aug 1998 11:56:16 -0700 (PDT)
On 12 Aug 1998, heddy Boubaker wrote:
>
> <> "marc" == marc <[EMAIL PROTECTED]> writes:
>
> marc> The normal solution for this is to simply set AllowOverride
> marc> None for /home, then set it to whatever you want for
> marc> the directories under home. Since AllowOverride None
> marc> makes it skip reading the htaccess file, it effectively
> marc> accomplishes the same thing that using /dev/null would.
>
> hi Marc,
>
> Unfortunately this doesn't seems to work, I have in my access.conf:
>
> <Directory /home>
> # allow SSI w/out exec
> Options +IncludesNoExec -ExecCGI
> # do not allow .htaccess because the server fail
> # to get /home/.htaccess - automount pb - and
> # then homepages became unreadable
> AllowOverride None
> #AccessFileName /dev/null
> order deny,allow
> allow from all
> </Directory>
>
> # All the following to not work because of the /home/.htaccess
> # problem above.
>
> <DirectoryMatch "^/home/[^/]+/public_html/">
> # allow SSI w/out exec
> Options +IncludesNoExec -ExecCGI
> # allow .htaccess
> AllowOverride Limit FileInfo AuthConfig
> </DirectoryMatch>
>
> <LocationMatch "^/~[^/]+/">
> # allow SSI w/out exec
> Options +IncludesNoExec -ExecCGI
> # allow .htaccess
> AllowOverride Limit FileInfo AuthConfig
> </LocationMatch>
You can't use AllowOverride within Location sections. Well, you can but
it makes no sense.
>
>
> And it seems that .htaccess are not read at all in ~ directories, in fact it
> seems - if I understand well the philosophy of AllowOverride - that what I
> got
> now is the correct behavior, the AllowOverride None in /home disable all the
> others AllowOverride in directories below ... so that I couldn't change them
> that's why I suggested the inclusion of AccessFileName in <Dir...> directives
> so that I could do:
No, the whole point of AllowOverride is to say what can be overridden in
.htaccess files.
If the above doesn't work then the below wouldn't work. Your
DirectoryMatch exprssion for public_html is probably incorrect.
Look closely to see if it is actually matching what you want it to
match, and consider if /home/*/public_html would work.
>
> <Directory /home>
> # could change AccessFileName in sub-dirs
> AllowOverride AccessFileName Limit FileInfo AuthConfig
> # do not read .htaccess in /home
> AccessFileName /dev/null
> </Directory>
>
> <DirectoryMatch "^/home/[^/]+/public_html/">
> # allow SSI w/out exec
> Options +IncludesNoExec -ExecCGI
> # allow .htaccess
> AccessFileName .htaccess
> # do not allow change of AccessFileName
> AllowOverride Limit FileInfo AuthConfig -AccessFileName
> </DirectoryMatch>
>
> You see what I mean ? Does it seems reasonable or am I completely wrong ?
>
> BTW is it possible to get values of already set variables w/out using <Perl>
> sections ? Kind of:
> AccessFileName ${AccessFileName}
No.
>
>
> thanks a lot for your time
>
> --
>
> - heddy -
>
