httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iga...@apache.org
Subject svn commit: r927824 - in /httpd/httpd/trunk/docs/manual: sections.html.en sections.xml
Date Fri, 26 Mar 2010 12:56:36 GMT
Author: igalic
Date: Fri Mar 26 12:56:36 2010
New Revision: 927824

URL: http://svn.apache.org/viewvc?rev=927824&view=rev
Log:
Adding an explanation about how URLs are ultimately mapped.

Modified:
    httpd/httpd/trunk/docs/manual/sections.html.en
    httpd/httpd/trunk/docs/manual/sections.xml

Modified: httpd/httpd/trunk/docs/manual/sections.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/sections.html.en?rev=927824&r1=927823&r2=927824&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/sections.html.en (original)
+++ httpd/httpd/trunk/docs/manual/sections.html.en Fri Mar 26 12:56:36 2010
@@ -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>,

Modified: httpd/httpd/trunk/docs/manual/sections.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/sections.xml?rev=927824&r1=927823&r2=927824&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/sections.xml (original)
+++ httpd/httpd/trunk/docs/manual/sections.xml Fri Mar 26 12:56:36 2010
@@ -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>,



Mime
View raw message