svn commit: r1934611 - httpd/httpd/branches/2.4.x/docs/manual/rewrite

[email protected]
Newsgroups gmane.comp.apache.cvs
Message-ID <177973331672.3396194.6469874175213431751@svn03-he-fi>
Author: rbowen
Date: Mon May 25 18:21:56 2026
New Revision: 1934611

Log:
docs: Insert mod_rewrite overview flowchart as Figure 1 in rewrite/tech

Add new per-request rewrite process diagram (Figure 1) showing both
per-server and per-directory phases with RewriteCond evaluation.
Renumber existing ruleset diagram to Figure 2.

Modified:
   httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml

Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml	Mon May 25 18:21:52 2026	(r1934610)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/tech.xml	Mon May 25 18:21:56 2026	(r1934611)
@@ -142,9 +142,17 @@ and URL matching.</p>
       engine is started with the contained ruleset (one or more
       rules together with their conditions). The operation of the
       URL rewriting engine itself is exactly the same for both
-      configuration contexts. Only the final result processing is
+     configuration contexts. Only the final result processing is
       different.</p>
 
+<p class="figure">
+      <img src="../images/mod_rewrite_fig1.png"
+          alt="Overview of per-request rewrite processing through
+          per-server and per-directory phases" /><br />
+      <dfn>Figure 1:</dfn>The per-request rewrite process showing
+      both per-server and per-directory rule processing phases
+</p>
+
       <p>The order of rules in the ruleset is important because the
       rewriting engine processes them in a special (and not very
       obvious) order. The rule is this: The rewriting engine loops
@@ -154,11 +162,11 @@ and URL matching.</p>
       existing corresponding conditions (<code>RewriteCond</code>
       directives). For historical reasons the conditions are given
       first, and so the control flow is a little bit long-winded. See
-      Figure 1 for more details.</p>
+      Figure 2 for more details.</p>
 <p class="figure">
       <img src="../images/rewrite_process_uri.png"
           alt="Flow of RewriteRule and RewriteCond matching" /><br />
-      <dfn>Figure 1:</dfn>The control flow through the rewriting ruleset
+      <dfn>Figure 2:</dfn>The control flow through the rewriting ruleset
 </p>
       <p>First the URL is matched against the
       <em>Pattern</em> of each rule. If it fails, <module>mod_rewrite</module>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.