mod_rewrite/3320: RewriteEngine On directive in

[Martin Argalas <Ma...@adpnet.cz>]

>Number:         3320
>Category:       mod_rewrite
>Synopsis:       RewriteEngine On directive in <Directory>
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Oct 30 17:40:01 PST 1998
>Last-Modified:
>Originator:     Martin.Argalas@adpnet.cz
>Organization:
apache
>Release:        1.3.3.
>Environment:
RedHat Linux 5.1 w/ 2.0.35 Kernel on a dual PII
gcc 2.7.2.3
>Description:
I've upgraded my apache from 1.2.6 to 1.3.3 and my RewriteMap mapname prg:/file...
stoped to work. Apache stopped to care about it. 

The rewrite module was configured like this:
<Virtualhost ...>
 RewriteLog  ....
 RewriteLogLevel 1  
 RewriteMap mapname prg:/file...  
</Virtualhost>

<Directory ...>
 RewriteEngine on
 RewriteRule ... 
</Directory>
 
I've discovered that Apache is not even initializing my program, until I've
moved the RewriteEngine On directive  to the <VirtualHost> definition context.
I truly don't know if this is a bug or the rewrite module is intended to  
behave like that. So far I have not found a word about this behaviour.
With the previous version of Apache I've had (1.2.6) it was working fine.
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> 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!         ]