<p>When <code class="directive"><a href="#rewriterule">RewriteRule</a></code>
is used in <code>VirtualHost</code> or server context with
version 2.2.22 or later of httpd, <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code>
- will only process the rewrite rules if the request URI is a <a href="./directive-dict.html#Syntax">URL-path</a>. This avoids
+ will only process the rewrite rules if the request URI is a <a href="directive-dict.html#Syntax">URL-path</a>. This avoids
some security issues where particular rules could allow
"surprising" pattern expansions (see <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-3368">CVE-2011-3368</a>
and <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4317">CVE-2011-4317</a>).
<p><a id="patterns" name="patterns"><em>Pattern</em></a> is
a perl compatible <a id="regexp" name="regexp">regular
expression</a>. On the first RewriteRule, it is matched against
- the (%-decoded) <a href="./directive-dict.html#Syntax">URL-path</a> (or
- <a href="./directive-dict.html#Syntax">file-path</a>, depending
+ the (%-decoded) <a href="directive-dict.html#Syntax">URL-path</a> (or
+ <a href="directive-dict.html#Syntax">file-path</a>, depending
on the context) of the request. Subsequent patterns are matched against the
output of the last matching RewriteRule.</p>