<li><p>In per-directory context (<directive module="core">Directory</directive> and .htaccess),
the <em>Pattern</em> is matched against only a partial path, for example a request
of "/app1/index.html" may result in comparison against "app1/index.html"
- or "index.html" depending on where the <directive>RewriteRule</directive> is
- defined.</p>
+ or "index.html" depending on the directory-path for which the
+ <directive>RewriteRule</directive> applies.</p>
- <p>The directory-path for which the rule is defined is stripped from the currently mapped
+ <p>The directory-path to which the rule applies is stripped from the currently mapped
filesystem path before comparison (up to and including a trailing slash).
The net result of this per-directory prefix stripping is that rules in
this context only match against the portion of the currently mapped filesystem path
- "below" where the rule is defined.</p>
+ "below" the directory-path to which the rule applies.</p>
<p>Directives such as <directive module="core"
>DocumentRoot</directive> and <directive module="mod_alias">Alias</directive>, or even the
directive for more information regarding what prefix will be added back to
relative substitutions.</li>
-<li> If you wish to match against the full URL-path in a per-directory
-(htaccess) RewriteRule, use the <code>%{REQUEST_URI}</code> variable in
+<li> If you wish to match against the full URL-path in a per-directory context
+RewriteRule, use the <code>%{REQUEST_URI}</code> variable in
a <directive module="mod_rewrite">RewriteCond</directive>.</li>
<li>The removed prefix always ends with a slash, meaning the matching occurs against a string which
<td>END</td>
<td>Stop the rewriting process immediately and don't apply any
more rules. Also prevents further execution of rewrite rules
- in per-directory and .htaccess context. (Available in 2.3.9 and later)
+ in per-directory context. (Available in 2.3.9 and later)
<em><a href="../rewrite/flags.html#flag_end">details ...</a></em></td>
</tr>
<tr>