From: Rich Bowen It provides a flexible and powerful way to manipulate URLs using an
unlimited number of rules. Each rule can have an
unlimited number of attached rule conditions, to allow you to rewrite URLs
- based on server variables, environment variables, cookies, HTTP headers,
- or timestamps. Rules can operate on the
+ based on server variables (including HTTP
+ headers, connection details, and timestamps), environment variables,
+ or other request properties. Rules can operate on the
URL-path (including any
trailing pathname information)
and can also alter the
@@ -507,7 +508,7 @@ RewriteRule "^/ex/(.*)" "${examplemap:$1}"
RewriteMap for more details.
%{ NAME_OF_VARIABLE
}
@@ -1227,7 +1228,7 @@ guide for complete details.
%N) to the last matched
RewriteCond pattern%{VARNAME})%0 is the entire match and
- %1..%9 are the captured groups. The server-variables are the same
+ %1..%9 are the captured groups. The server variables are the same
as for the TestString of a
diff --git a/docs/manual/rewrite/flags.xml b/docs/manual/rewrite/flags.xml
index f2b54a1a17..b5cf4a417a 100644
--- a/docs/manual/rewrite/flags.xml
+++ b/docs/manual/rewrite/flags.xml
@@ -75,7 +75,7 @@ so backreferences are unescaped at the time they are applied.
Using the B flag, non-alphanumeric characters in backreferences
will be escaped. For example, consider the rule:B
Escape non-alphanumeric characters in backreferences before
- applying the transformation. For similar escaping of server-variables, see
+ applying the transformation. For similar escaping of server variables, see
the "escape" mapping-function.details ...
For similar escaping of server-variables, see +
For similar escaping of server variables, see the "escape" mapping-function