You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by el...@apache.org on 2018/03/30 15:43:59 UTC
svn commit: r1828070 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
Author: elukey
Date: Fri Mar 30 15:43:58 2018
New Revision: 1828070
URL: http://svn.apache.org/viewvc?rev=1828070&view=rev
Log:
docs rebuild
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en?rev=1828070&r1=1828069&r2=1828070&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy.html.en Fri Mar 30 15:43:58 2018
@@ -1111,6 +1111,18 @@ ProxyPass "/mirror/foo" "http://backen
<code>backend.example.com</code> <em>except</em> requests made to
<code>/mirror/foo/i</code>.</p>
+ <p>Mixing ProxyPass settings in different contexts does not work:</p>
+ <pre class="prettyprint lang-config">ProxyPass "/mirror/foo/i" "!"
+<Location "/mirror/foo/">
+ ProxyPass "http://backend.example.com/"
+</Location></pre>
+
+ <p>In this case, a request to <code>/mirror/foo/i</code> will get proxied,
+ because the <code class="directive">ProxyPass</code> directive in the Location block will be evaluated
+ first. The fact that <code class="directive">ProxyPass</code> supports both server and directory contexts
+ does not mean that their scope and position in the configuration file will
+ guarantee any ordering or override.</p>
+
<div class="warning"><h3>Ordering ProxyPass Directives</h3>
<p>The configured <code class="directive"><a href="#proxypass">ProxyPass</a></code>
and <code class="directive"><a href="#proxypassmatch">ProxyPassMatch</a></code>
@@ -1119,12 +1131,15 @@ ProxyPass "/mirror/foo" "http://backen
<code class="directive"><a href="#proxypass">ProxyPass</a></code> rules starting with the
longest URLs first. Otherwise, later rules for longer URLS will be hidden
by any earlier rule which uses a leading substring of the URL. Note that
- there is some relation with worker sharing. In contrast, only one
- <code class="directive"><a href="#proxypass">ProxyPass</a></code> directive can be placed
- in a <code class="directive"><a href="../mod/core.html#location">Location</a></code> block, and the most
- specific location will take precedence.</p>
-
- <p>For the same reasons, exclusions must come <em>before</em> the
+ there is some relation with worker sharing.</p>
+ </div>
+ <div class="warning"><h3>Ordering ProxyPass Directives in Locations</h3>
+ <p>Only one <code class="directive"><a href="#proxypass">ProxyPass</a></code> directive
+ can be placed in a <code class="directive"><a href="../mod/core.html#location">Location</a></code> block,
+ and the most specific location will take precedence.</p>
+ </div>
+ <div class="warning"><h3>Exclusions and the no-proxy environment variable</h3>
+ <p>Exclusions must come <em>before</em> the
general <code class="directive">ProxyPass</code> directives. In 2.4.26 and later, the "no-proxy"
environment variable is an alternative to exclusions, and is the only
way to configure an exclusion of a <code class="directive">ProxyPass</code>