www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alejandro "Vázquez" <a...@iniciando.com>
Subject config/5583: AllowOverride doesn't work when used within a <DirectoryMatch> or <Directory ~> directive.
Date Fri, 14 Jan 2000 01:08:10 GMT

>Number:         5583
>Category:       config
>Synopsis:       AllowOverride doesn't work when used within a <DirectoryMatch> or
<Directory ~> directive.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Jan 13 17:10:00 PST 2000
>Originator:     alex@iniciando.com
>Release:        1.3.9
Linux sss.iniciando.net 2.2.5-15smp #1 SMP Mon Apr 19 22:43:28 EDT 1999 i686 unknown
RedHat 6.0 (default kernel, default gcc compiler).
Custom built Apache 1.3.9 (with PHP3.0.13, mod_ssl 2.4.9, mod_frontpage/
AllowOverride within a <DirectoryMatch> or <Directory ~> directive
does not override any pervious setting made thru another <Directory> directory.
<Directory />
  Options None
  AllowOverride None
  order deny,allow
  deny from all

<DirectoryMatch "/opt/.*/htdocs">
  Options Indexes FollowSymLinks
  AllowOverride AuthConfig, Limit
  order allow,deny
  allow from all

# If you try to access /opt/mydomain.com/htdocs/index.html
# it works perfect. (The order...allow settings within <Directory>
# gets overriden by those in <DirectoryMatch>).
# But it won't read /opt/mydomain.com/htdocs/.htaccess to see
# if any local settings are there (The AllowOverride in <Directory>
# doesn't get overriden by the one in <DirectoryMatch>).
# When the root AllowOverride specify some options, .htaccess gets read
# but it the server behaves like if the <DirectoryMatch>'s AllowOverride
# isn't there.
Use <Directory> when you have to override an AllowOverride. When you don't
have do to that, the others directives seem to work well.
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message