From 7566ed1b2bc918ca1fa86a21d9ba3c85da4ab1bd Mon Sep 17 00:00:00 2001 From: Daniel Gruno Date: Fri, 20 Apr 2012 10:34:19 +0000 Subject: [PATCH] xforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1328306 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/rewrite/avoid.html.en | 4 ++-- docs/manual/rewrite/index.html.en | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/manual/rewrite/avoid.html.en b/docs/manual/rewrite/avoid.html.en index bfe4b3a0b6..1fedff908e 100644 --- a/docs/manual/rewrite/avoid.html.en +++ b/docs/manual/rewrite/avoid.html.en @@ -170,7 +170,7 @@ RewriteRule ^/?images(.*) http://imageserver.local/images$1 [P]

However, in many cases, when there is no actual pattern matching -meeded, as in the example shown above, the ProxyPass directive is a better choice. +needed, as in the example shown above, the ProxyPass directive is a better choice. The example here could be rendered as:

@@ -196,7 +196,7 @@ accomplish.

Environment Variable Testing

mod_rewrite is frequently used to take a particular -action based on the presence or absense of a particular environment +action based on the presence or absence of a particular environment variable or request header. This can be done more efficiently using the <If>.

diff --git a/docs/manual/rewrite/index.html.en b/docs/manual/rewrite/index.html.en index f826dcce31..759c352e69 100644 --- a/docs/manual/rewrite/index.html.en +++ b/docs/manual/rewrite/index.html.en @@ -51,7 +51,7 @@

Since mod_rewrite is so powerful, it can indeed be rather complex. This document supplements the reference documentation, and attempts to allay some of that complexity, and provide highly - annoted examples of common scenarios that you may handle with + annotated examples of common scenarios that you may handle with mod_rewrite. But we also attempt to show you when you should not use mod_rewrite, and use other standard Apache features instead, thus avoiding this unnecessary complexity.

-- 2.40.0