AllowOverride - Doc bug vs. Code bug

[Brad Nicholes <BN...@novell.com>]

    Could somebody clarify this?  The documentation for AllowOverride states that the default for the directive is "AllowOverride All".  But if you add an alias to a directory and do not include a <Directory ..> block for the aliased directory or if you simply exclude the AllowOverride directive from the <Directory...> block, Apache will ignore the .htaccess file even if it exists.  The default in create_core_dir_config() is to set the override field to OR_UNSET.  This would imply that the default behavior of AllowOverride would be either undetermined or to inherit the parent directory's overrides.  Is this a bug in the documentation or the source code?  Or can somebody explain how the documentation reflects the source code?

thanks,
Brad

Brad Nicholes
Senior Software Engineer
Novell, Inc., the leading provider of Net business solutions
http://www.novell.com 

Re: AllowOverride - Doc bug vs. Code bug

[André Malo <nd...@perlig.de>]

* Brad Nicholes wrote:

> Could somebody clarify this?  The documentation for AllowOverride
> states that the default for the directive is "AllowOverride All". 

That's right as far I can see.

> But if you add an alias to a directory and do not include a <Directory
> ..> block for the aliased directory or if you simply exclude the
> AllowOverride directive from the <Directory...> block, Apache will
> ignore the .htaccess file even if it exists.  

ehm...sorry,
maybe you forgot to remove the default

<Directory />
  AllowOverride None
<Directory>

container...?

> The default in create_core_dir_config() is to set the override field
> to OR_UNSET.  

huh?

conf->override = dir ? OR_UNSET : OR_UNSET|OR_ALL;

nd
-- 
package Hacker::Perl::Another::Just;print
qq~@{[reverse split/::/ =>__PACKAGE__]}~;

#  André Malo  #  http://www.perlig.de  #