Received: (qmail 23941 invoked by uid 2012); 26 Nov 1998 13:57:13 -0000 Message-Id: <19981126135713.23940.qmail@hyperreal.org> Date: 26 Nov 1998 13:57:13 -0000 From: Sheldon Hearn Reply-To: axl@iafrica.com To: apbugs@hyperreal.org Subject: AllowOverride Limit ignored for regex in access.conf X-Send-Pr-Version: 3.2 >Number: 3454 >Category: mod_access >Synopsis: AllowOverride Limit ignored for regex in access.conf >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Nov 26 07:10:00 PST 1998 >Closed-Date: Mon Oct 30 18:45:07 PST 2000 >Last-Modified: Mon Oct 30 18:45:07 PST 2000 >Originator: axl@iafrica.com >Release: 1.3.3 >Organization: >Environment: FreeBSD 2.2-STABLE (RELENG_2_2) gcc -O -pipe -fomit-frame-pointer >Description: In access.conf, if I wrap the following in , .htaccess Limit is enforced. If the following is wrapped in , .htaccess Limit is not enforced: Options Indexes FollowSymLinks Includes AllowOverride AuthConfig Limit The access.conf's sets a more restrictive ``AllowOverride None''. This looks like an incomplete implimentation of the new regexp matching code for and directives. >How-To-Repeat: Try to use a regexp directive to AllowOverride so that .htaccess s are enforced in homedirs. >Fix: This may be a symptom of the same problem causing the likes of PR1829. I suspect it may also be the cause of the problem reported in PR3019. >Release-Note: >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: dgaudet State-Changed-When: Thu Aug 5 10:31:48 PDT 1999 State-Changed-Why: This is actually how things are documented -- .htaccess occurs while the non-regex directory sections are parsed. Try using Dean State-Changed-From-To: feedback-closed State-Changed-By: slive State-Changed-When: Mon Oct 30 18:45:02 PST 2000 State-Changed-Why: [This is a standard response.] No response from submitter, assuming issue has been resolved. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [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! ]