From b34f14e6ae1483083ce331d4cf4919010d27a6c3 Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Fri, 28 May 2010 14:39:46 +0000 Subject: [PATCH] Several typos fixed. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@949190 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/rewrite/avoid.html.en | 14 +++++++++----- docs/manual/rewrite/avoid.xml | 9 +++++++-- docs/manual/rewrite/flags.html.en | 2 +- 3 files changed, 17 insertions(+), 8 deletions(-) diff --git a/docs/manual/rewrite/avoid.html.en b/docs/manual/rewrite/avoid.html.en index 65709de040..1466e6773a 100644 --- a/docs/manual/rewrite/avoid.html.en +++ b/docs/manual/rewrite/avoid.html.en @@ -112,7 +112,7 @@ task in a .htaccess file instead.

The Alias directive provides mapping from a URI to a directory - usually a directory outside of your DocumentRoot. Although it -is possible to perform this mappint with mod_rewrite, +is possible to perform this mapping with mod_rewrite, Alias is the preferred method, for reasons of simplicity and performance.

@@ -137,10 +137,10 @@ server.

with mod_rewrite, it is seldom the right way. Creating individual <VirtualHost> blocks is almost always the right way to go. In the event that you have an enormous number of virtual hosts, consider using -mod_vhost_alias to crate these hosts automatically.

+mod_vhost_alias to create these hosts automatically.

-

Third-party modules sucha as mod_macro are -also useful for creating a large number of virtual hosts dymaically.

+

Third-party modules such as mod_macro are +also useful for creating a large number of virtual hosts dynamically.

Using mod_rewrite for vitualhost creation may be appropriate if you are using a hosting service that does not provide @@ -154,7 +154,11 @@ seems like the right approach.

top

Simple Proxying

-

ProxyPass

+ +

RewriteRule provides the [P] flag to pass rewritten URIs through +mod_proxy. As with any use of mod_rewrite, +you want to ask yourself whether it's really the best solution.

+
top

Environment Variable Testing

diff --git a/docs/manual/rewrite/avoid.xml b/docs/manual/rewrite/avoid.xml index d51bc9e2bc..954f1ef136 100644 --- a/docs/manual/rewrite/avoid.xml +++ b/docs/manual/rewrite/avoid.xml @@ -122,7 +122,7 @@ task in a .htaccess file instead.

The Alias directive provides mapping from a URI to a directory - usually a directory outside of your DocumentRoot. Although it -is possible to perform this mappint with mod_rewrite, +is possible to perform this mapping with mod_rewrite, Alias is the preferred method, for reasons of simplicity and performance.

@@ -164,7 +164,12 @@ seems like the right approach.

Simple Proxying -

ProxyPass

+ +

RewriteRule provides the [P] flag to pass rewritten URIs through +mod_proxy. As with any use of mod_rewrite, +you want to ask yourself whether it's really the best solution.

+
Environment Variable Testing diff --git a/docs/manual/rewrite/flags.html.en b/docs/manual/rewrite/flags.html.en index e8addb906c..232f827469 100644 --- a/docs/manual/rewrite/flags.html.en +++ b/docs/manual/rewrite/flags.html.en @@ -223,7 +223,7 @@ variables work.

contexts, including CGI programs, other RewriteRule directives, or CustomLog directives.

-

The following example sets an evironment variable called 'image' to a +

The following example sets an environment variable called 'image' to a value of '1' if the requested URI is an image file. Then, that environment variable is used to exclude those requests from the access log.

-- 2.50.1