AllowOverride in <Directory>

Hi,

In the documentation of Apache 2.0, it is said that AllowOverride is
only available in <Directory> without regular expressions
(http://httpd.apache.org/docs-2.0/mod...#allowoverride)

+--------------------------------------------------
| Only available in <Directory> sections
| AllowOverride is valid only in <Directory> sections specified
| without regular expressions, not in <Location>, <DirectoryMatch> or
| <Files> sections.
+--------------------------------------------------

Now it seems that it is also not available when wild-cards are used in
the directory path. Can anyone confirm or disconfirm this? If it is
indeed so, I'd say it's an omission in the documentation.

Thanks,

--
Dr. Frederik Fouvry Universität des Saarlandes, Computerlinguistik
Gebäude 17/3.02 - Postfach 15 11 50 - D-66041 Saarbrücken, Germany
telephone: +49(0)681 302 4176 facsimile: +49(0)681 302 4700
fouvry@coli.uni-sb.de http://www.coli.uni-saarland.de/~fouvry/

On Wed, 12 Jan 2005, Frederik Fouvry <fouvry@coli.uni-saarland.de> wrote:
>
> Hi,
>
> In the documentation of Apache 2.0, it is said that AllowOverride is
> only available in <Directory> without regular expressions
> (http://httpd.apache.org/docs-2.0/mod...#allowoverride)
>
> +--------------------------------------------------
>| Only available in <Directory> sections
>| AllowOverride is valid only in <Directory> sections specified
>| without regular expressions, not in <Location>, <DirectoryMatch> or
>| <Files> sections.
> +--------------------------------------------------
>
> Now it seems that it is also not available when wild-cards are used in
> the directory path. Can anyone confirm or disconfirm this? If it is
> indeed so, I'd say it's an omission in the documentation.

Give an example of a <Directory> section with a wildcard and example of a
full systen path it fails to work for. I believe that wildcard * does not
include directory separators (like '/'), so the wildcard can only refer to
a single directory in specified system path.

| > In the documentation of Apache 2.0, it is said that AllowOverride is
| > only available in <Directory> without regular expressions
| > (http://httpd.apache.org/docs-2.0/mod...#allowoverride)
| >
| > +--------------------------------------------------
| >| Only available in <Directory> sections
| >| AllowOverride is valid only in <Directory> sections specified
| >| without regular expressions, not in <Location>, <DirectoryMatch> or
| >| <Files> sections.
| > +--------------------------------------------------
| >
| > Now it seems that it is also not available when wild-cards are used in
| > the directory path. Can anyone confirm or disconfirm this? If it is
| > indeed so, I'd say it's an omission in the documentation.
|
| Give an example of a <Directory> section with a wildcard and example of a
| full systen path it fails to work for. I believe that wildcard * does not
| include directory separators (like '/'), so the wildcard can only refer to
| a single directory in specified system path.

There are no problems with full paths.

An example of what is not working:

<Directory /home/???/*/public_html>
AllowOverride Options
</Directory>

I can put anything in .htaccess, and the server never complains => the
file is not read.

Frederik Fouvry

Frederik Fouvry<fouvry@coli.uni-saarland.de> wrote:
>
> | > In the documentation of Apache 2.0, it is said that AllowOverride is
> | > only available in <Directory> without regular expressions
> | > (http://httpd.apache.org/docs-2.0/mod...#allowoverride)
> | >
> | > Now it seems that it is also not available when wild-cards are used in
> | > the directory path. Can anyone confirm or disconfirm this? If it is
> | > indeed so, I'd say it's an omission in the documentation.
>
> An example of what is not working:
>
> <Directory /home/???/*/public_html>
> AllowOverride Options
> </Directory>
>
> I can put anything in .htaccess, and the server never complains => the
> file is not read.

NOT confirmed (2.0.52, albeit on Windows 98SE).

Replacing single path components with an "*" or an
apropriate number of "?" makes no difference at all.


--n