From: Rich Bowen
$N and
%N (see below). These are available for creating
the strings Substitution and TestString.
- Figure 2 shows to which locations the back-references are
- transferred for expansion.
+ Figure 1 shows to which locations the back-references are
+ transferred for expansion as well as illustrating the flow of the
+ RewriteRule, RewriteCond matching.
- ![[Needs graphics capability to display]](../images/mod_rewrite_fig2.gif)
- Figure 2: The back-reference flow through a rule.
+ 
+ Figure 1: The back-reference flow through a rule.
$N and
%N (see below). These are available for creating
the strings Substitution and TestString.
- Figure 2 shows to which locations the back-references are
- transferred for expansion.
+ Figure 1 shows to which locations the back-references are
+ transferred for expansion as well as illustrating the flow of the
+ RewriteRule, RewriteCond matching.
- ![[Needs graphics capability to display]](../images/mod_rewrite_fig2.gif)
- Figure 2: The back-reference flow through a rule.
+ 
+ Figure 1: The back-reference flow through a rule.
- ![[Needs graphics capability to display]](../images/mod_rewrite_fig1.gif)
+ 
Figure 1:The control flow through the rewriting ruleset
As you can see, first the URL is matched against the diff --git a/docs/manual/rewrite/tech.xml b/docs/manual/rewrite/tech.xml index e7de78a76fb..b0fcb4d8fd5 100644 --- a/docs/manual/rewrite/tech.xml +++ b/docs/manual/rewrite/tech.xml @@ -133,8 +133,8 @@ and URL matching.
first, and so the control flow is a little bit long-winded. See Figure 1 for more details.
- ![[Needs graphics capability to display]](../images/mod_rewrite_fig1.gif)
+ 
Figure 1:The control flow through the rewriting ruleset
As you can see, first the URL is matched against the