you specify a <em>Substitution</em> string of
<code>/www/file.html</code>, then this will be treated as a
URL-path <em>unless</em> a directory named <code>www</code>
- exists at the root or your file-system (or, in the case of
- using rewrites in a <code>.htaccess</code> file, relative to
+ exists at the root of your file-system (or, in the case of
+ per-directory rewrites, relative to
your document root), in which case it will
be treated as a file-system path. If you wish other
URL-mapping directives (such as <directive
<tr>
<td>last|L</td>
<td>Stop the rewriting process immediately and don't apply any
- more rules. Especially note caveats for per-directory and
- .htaccess context (see also the END flag). <em><a
+ more rules. Especially note caveats for per-directory context (see also the END flag). <em><a
href="../rewrite/flags.html#flag_l">details ...</a></em></td>
</tr>
<tr>
Some flags take one or more arguments. Flags are not case sensitive.</p>
<p>Flags that alter metadata associated with the request (T=, H=, E=)
-have no affect in per-directory and htaccess context, when a substitution
+have no effect in per-directory context, when a substitution
(other than '-') is performed during the same round of rewrite processing.
</p>
<p>Note that environment variables do not survive an external
redirect. You might consider using the [CO] flag to set a
-cookie. For per-directory and htaccess rewrites, where the final
+cookie. For per-directory rewrites, where the final
substitution is processed as an internal redirect, environment
variables from the previous round of rewriting are prefixed with
"REDIRECT_". </p>