F|forbidden
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 Deny directive, this
+the Deny directive, this
allows more flexibility in assigning a Forbidden status.
The following rule will forbid .exe
files from being
@@ -522,7 +522,7 @@ use of the [PT] flag causes the result of the RewriteRule to be passed back through
URL mapping, so that location-based mappings, such as Alias, Redirect, or Redirect, or ScriptAlias, for example, might have a
chance to take effect.
diff --git a/docs/manual/rewrite/proxy.xml b/docs/manual/rewrite/proxy.xml
index c7a8663e6a..41b2d56fef 100644
--- a/docs/manual/rewrite/proxy.xml
+++ b/docs/manual/rewrite/proxy.xml
@@ -94,7 +94,7 @@ ProxyPassReverse / http://old.example.com/
Consider using either ProxyPass or ProxyPassMatch whenever possible in
+ module="mod_proxy">ProxyPassMatch whenever possible in
preference to mod_rewrite.
diff --git a/docs/manual/rewrite/remapping.xml b/docs/manual/rewrite/remapping.xml
index 974fb1030e..a5db6e8ff3 100644
--- a/docs/manual/rewrite/remapping.xml
+++ b/docs/manual/rewrite/remapping.xml
@@ -249,7 +249,7 @@ RewriteRule ^(.*).html$ $1.php
<Directory> block or in a .htaccess file), so that the
-f
checks are looking at the correct directory path.
You may need to set a RewriteBase directive to specify the
+ module="mod_rewrite">RewriteBase directive to specify the
directory base that you're working in.
@@ -275,7 +275,7 @@ RewriteRule ^(.*).html$ $1.php
The very best way to solve this doesn't involve mod_rewrite at all,
-but rather uses the Redirect
+but rather uses the Redirect
directive placed in a virtual host for the non-canonical
hostname(s).