<code>RewriteEngine on</code> directive for each virtual host
in which you wish to use rewrite rules.</p>
+ <p><code class="directive">RewriteMap</code> directives of the type <code>prg</code>
+ are not started during server initialization if they're defined in a
+ context that does not have <code class="directive">RewriteEngine</code> set to
+ <code>on</code></p>
+
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="RewriteLock" id="RewriteLock">RewriteLock</a> <a name="rewritelock" id="rewritelock">Directive</a></h2>
program which will implement a 1:1 map (<em>i.e.</em>,
key == value) could be:</p>
+ <p>External rewriting programs are not started they're defined in a
+ context that does not have <code class="directive">RewriteEngine</code> set to
+ <code>on</code></p>.
+
<div class="example"><pre>
#!/usr/bin/perl
$| = 1;
inherited by virtual hosts. This means that you need to have a
<code>RewriteEngine on</code> directive for each virtual host
in which you wish to use rewrite rules.</p>
+
+ <p><directive>RewriteMap</directive> directives of the type <code>prg</code>
+ are not started during server initialization if they're defined in a
+ context that does not have <directive>RewriteEngine</directive> set to
+ <code>on</code></p>
</usage>
</directivesynopsis>
program which will implement a 1:1 map (<em>i.e.</em>,
key == value) could be:</p>
+ <p>External rewriting programs are not started they're defined in a
+ context that does not have <directive>RewriteEngine</directive> set to
+ <code>on</code></p>.
+
<example>
<pre>
#!/usr/bin/perl