From 6b59a2a80b382e485ebddae82d81d03143c2ef6a Mon Sep 17 00:00:00 2001
From: =?utf8?q?Igor=20Gali=C4=87?= <igalic@apache.org>
Date: Fri, 26 Mar 2010 12:56:36 +0000
Subject: [PATCH] Adding an explanation about how URLs are ultimately mapped.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@927824 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/sections.html.en | 24 ++++++++++++++++++++++++
 docs/manual/sections.xml     | 24 ++++++++++++++++++++++++
 2 files changed, 48 insertions(+)

diff --git a/docs/manual/sections.html.en b/docs/manual/sections.html.en
index 4b9b2e94bf..b579f223fe 100644
--- a/docs/manual/sections.html.en
+++ b/docs/manual/sections.html.en
@@ -213,6 +213,30 @@ SetHandler server-status<br />
 </code></p></div>
 
 
+<h3><a name="overlapping-webspace" id="overlapping-webspace">Overlapping Webspace</a></h3>
+In order to have two overlapping URLs one has to consider the order in which
+certain sections or directives are evaluated. For
+<code class="directive"><a href="./mod/core.html#location">&lt;Location&gt;</a></code> this would be:
+<div class="example"><p><code>
+&lt;Location /foo&gt;<br />
+&lt;/Location&gt;<br />
+&lt;Location /foo/bar&gt;<br />
+&lt;/Location&gt;
+</code></p></div>
+<code class="directive"><a href="./mod/core.html#alias">&lt;Alias&gt;</a></code>es on the other hand,
+are mapped vice-versa:
+<div class="example"><p><code>
+Alias /foo/bar /srv/www/uncommon/bar<br />
+Alias /foo /srv/www/common/foo<br />
+</code></p></div>
+Same goes for the <code class="directive"><a href="./mod/mod_proxy.html#proxypass">ProxyPass</a></code>
+directives:
+<div class="example"><p><code>
+ProxyPass /special-area http://special.example.com smax=5 max=10
+ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On
+</code></p></div>
+ 
+
 <h3><a name="wildcards" id="wildcards">Wildcards and Regular Expressions</a></h3>
 
 <p>The <code class="directive"><a href="./mod/core.html#directory">&lt;Directory&gt;</a></code>,
diff --git a/docs/manual/sections.xml b/docs/manual/sections.xml
index 2f6afa93df..3ef6a1c256 100644
--- a/docs/manual/sections.xml
+++ b/docs/manual/sections.xml
@@ -236,6 +236,30 @@ SetHandler server-status<br />
 </example>
 </section>
 
+<section id="overlapping-webspace"><title>Overlapping Webspace</title>
+In order to have two overlapping URLs one has to consider the order in which
+certain sections or directives are evaluated. For
+<directive type="section" module="core">Location</directive> this would be:
+<example>
+&lt;Location /foo&gt;<br />
+&lt;/Location&gt;<br />
+&lt;Location /foo/bar&gt;<br />
+&lt;/Location>
+</example>
+<directive type="section" module="core">Alias</directive>es on the other hand,
+are mapped vice-versa:
+<example>
+Alias /foo/bar /srv/www/uncommon/bar<br />
+Alias /foo /srv/www/common/foo<br />
+</example>
+The same is true for the <directive module="mod_proxy">ProxyPass</directive>
+directives:
+<example>
+ProxyPass /special-area http://special.example.com smax=5 max=10
+ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On
+</example>
+</section> 
+
 <section id="wildcards"><title>Wildcards and Regular Expressions</title>
 
 <p>The <directive type="section" module="core">Directory</directive>,
-- 
2.50.1