<section id="flag_f"><title>F|forbidden</title>
<p>Using the [F] flag causes the server to return a 403 Forbidden status
code to the client. While the same behavior can be accomplished using
-the <directive module="mod_access">Deny</directive> directive, this
+the <directive module="mod_access_compat">Deny</directive> directive, this
allows more flexibility in assigning a Forbidden status.</p>
<p>The following rule will forbid <code>.exe</code> files from being
module="mod_rewrite">RewriteRule</directive> to be passed back through
URL mapping, so that location-based mappings, such as <directive
module="mod_alias">Alias</directive>, <directive
-module="core">Redirect</directive>, or <directive
+module="mod_alias">Redirect</directive>, or <directive
module="mod_alias">ScriptAlias</directive>, for example, might have a
chance to take effect.
</p>
<p>Consider using either <directive
module="mod_proxy">ProxyPass</directive> or <directive
- module="mod_rewrite">ProxyPassMatch</directive> whenever possible in
+ module="mod_proxy">ProxyPassMatch</directive> whenever possible in
preference to mod_rewrite.</p>
</dd>
</dl>
<Directory> block or in a .htaccess file), so that the
<code>-f</code> checks are looking at the correct directory path.
You may need to set a <directive
- module="mod_rewite">RewriteBase</directive> directive to specify the
+ module="mod_rewrite">RewriteBase</directive> directive to specify the
directory base that you're working in.</p>
</dd>
</dl>
<dd>
<p>The very best way to solve this doesn't involve mod_rewrite at all,
-but rather uses the <directive module="alias">Redirect</directive>
+but rather uses the <directive module="mod_alias">Redirect</directive>
directive placed in a virtual host for the non-canonical
hostname(s).</p>