From e9021c05de7fcc027252497f9f66ee8f2fe0eb9e Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Fri, 1 Jan 2010 21:27:55 +0000 Subject: Adds helpful diagrams to the rewrite intro document, provided by Joseph Pecoraro. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@895078 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/rewrite/intro.xml | 17 +++++++++++++++-- 1 file changed, 15 insertions(+), 2 deletions(-) (limited to 'docs/manual/rewrite/intro.xml') diff --git a/docs/manual/rewrite/intro.xml b/docs/manual/rewrite/intro.xml index a19e5bbe37..f7f90a6699 100644 --- a/docs/manual/rewrite/intro.xml +++ b/docs/manual/rewrite/intro.xml @@ -160,7 +160,7 @@ the expression.

-
RewriteRule basics +
RewriteRule Basics

A RewriteRule consists of three arguments separated by spaces. The arguments are

    @@ -174,6 +174,13 @@ expression matched against the URL-Path of the incoming request (the part after the hostname but before any question mark indicating the beginning of a query string).

    +

    + Syntax of the RewriteRule directive
    + Figure 2: Syntax of the RewriteRule directive. +

    + +

    The Substitution can itself be one of three things:

    @@ -243,7 +250,7 @@ examples, see the Rewrite Flags document.

-
Rewrite conditions +
Rewrite Conditions

One or more RewriteCond directives can be used to restrict the types of requests that will be subject to the @@ -253,6 +260,12 @@ request, the second argument is a regular expression that must match the variable, and a third optional argument is a list of flags that modify how the match is evaluated.

+

+ Syntax of the RewriteCond directive
+ Figure 3: Syntax of the RewriteCond directive +

+

For example, to send all requests from a particular IP range to a different server, you could use:

-- cgit v1.2.1