the <code>[P,NE]</code> option to prevent the <code>'|'</code> character
from being escaped.</div>
+ <p>When used inside a <code class="directive"><a href="../mod/core.html#location"><Location></a></code> section, the first argument is omitted and the local
+ directory is obtained from the <code class="directive"><a href="../mod/core.html#location"><Location></a></code>. The same will occur inside a
+ <code class="directive"><a href="../mod/core.html#locationmatch"><LocationMatch></a></code> section;
+ however, ProxyPass does not interpret the regexp as such, so it is necessary
+ to use <code class="directive">ProxyPassMatch</code> in this situation instead.</p>
+
<p>Suppose the local server has address <code>http://example.com/</code>;
then</p>
<code>http://example.com/mirror/foo/bar</code> to be internally converted
into a proxy request to <code>http://backend.example.com/bar</code>.</p>
+ <p>The ProxyPass directive is not supported in <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> or <code class="directive"><a href="../mod/core.html#files"><Files></a></code> sections.</p>
+
+ <p>If you require a more flexible reverse-proxy configuration, see the
+ <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directive with the
+ <code>[P]</code> flag.</p>
+
<p>The following alternative syntax is possible; however, it can carry a
performance penalty when present in very large numbers. The advantage of
the below syntax is that it allows for dynamic control via the
</div>
+ <p><strong>ProxyPass <code>key=value</code> Parameters</strong></p>
+
<p>In Apache HTTP Server 2.1 and later, mod_proxy supports pooled
connections to a backend server. Connections created on demand
can be retained in a pool for future use. Limits on the pool size
<p>Setting up a hot-standby that will only be used if no other
- members are available</p>
+ members are available:</p>
<pre class="prettyprint lang-config">ProxyPass "/" "balancer://hotcluster/"
<Proxy balancer://hotcluster>
BalancerMember ajp://1.2.3.4:8009 loadfactor=1
</Proxy></pre>
+ <p><strong>Additional ProxyPass Keywords</strong></p>
+
<p>Normally, mod_proxy will canonicalise ProxyPassed URLs.
But this may be incompatible with some backends, particularly those
that make use of <var>PATH_INFO</var>. The optional <var>nocanon</var>
The optional <var>noquery</var> keyword (available in
httpd 2.4.1 and later) prevents this.</p>
- <p>When used inside a <code class="directive"><a href="../mod/core.html#location"><Location></a></code> section, the first argument is omitted and the local
- directory is obtained from the <code class="directive"><a href="../mod/core.html#location"><Location></a></code>. The same will occur inside a
- <code class="directive"><a href="../mod/core.html#locationmatch"><LocationMatch></a></code> section;
- however, ProxyPass does not interpret the regexp as such, so it is necessary
- to use <code class="directive">ProxyPassMatch</code> in this situation instead.</p>
-
- <p>This directive is not supported in <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> or <code class="directive"><a href="../mod/core.html#files"><Files></a></code> sections.</p>
-
- <p>If you require a more flexible reverse-proxy configuration, see the
- <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directive with the
- <code>[P]</code> flag.</p>
-
<p>The optional <var>interpolate</var> keyword, in combination with
<code class="directive">ProxyPassInterpolateEnv</code>, causes the ProxyPass
to interpolate environment variables, using the syntax
the <code>[P,NE]</code> option to prevent the <code>'|'</code> character
from being escaped.</note>
+ <p>When used inside a <directive type="section" module="core"
+ >Location</directive> section, the first argument is omitted and the local
+ directory is obtained from the <directive type="section" module="core"
+ >Location</directive>. The same will occur inside a
+ <directive type="section" module="core">LocationMatch</directive> section;
+ however, ProxyPass does not interpret the regexp as such, so it is necessary
+ to use <directive>ProxyPassMatch</directive> in this situation instead.</p>
+
<p>Suppose the local server has address <code>http://example.com/</code>;
then</p>
<code>http://example.com/mirror/foo/bar</code> to be internally converted
into a proxy request to <code>http://backend.example.com/bar</code>.</p>
+ <p>The ProxyPass directive is not supported in <directive type="section" module="core"
+ >Directory</directive> or <directive type="section" module="core"
+ >Files</directive> sections.</p>
+
+ <p>If you require a more flexible reverse-proxy configuration, see the
+ <directive module="mod_rewrite">RewriteRule</directive> directive with the
+ <code>[P]</code> flag.</p>
+
<p>The following alternative syntax is possible; however, it can carry a
performance penalty when present in very large numbers. The advantage of
the below syntax is that it allows for dynamic control via the
</note> <!-- /ordering_proxypass -->
+ <p><strong>ProxyPass <code>key=value</code> Parameters</strong></p>
+
<p>In Apache HTTP Server 2.1 and later, mod_proxy supports pooled
connections to a backend server. Connections created on demand
can be retained in a pool for future use. Limits on the pool size
</highlight>
<p>Setting up a hot-standby that will only be used if no other
- members are available</p>
+ members are available:</p>
<highlight language="config">
ProxyPass "/" "balancer://hotcluster/"
<Proxy balancer://hotcluster>
</Proxy>
</highlight>
+ <p><strong>Additional ProxyPass Keywords</strong></p>
+
<p>Normally, mod_proxy will canonicalise ProxyPassed URLs.
But this may be incompatible with some backends, particularly those
that make use of <var>PATH_INFO</var>. The optional <var>nocanon</var>
The optional <var>noquery</var> keyword (available in
httpd 2.4.1 and later) prevents this.</p>
- <p>When used inside a <directive type="section" module="core"
- >Location</directive> section, the first argument is omitted and the local
- directory is obtained from the <directive type="section" module="core"
- >Location</directive>. The same will occur inside a
- <directive type="section" module="core">LocationMatch</directive> section;
- however, ProxyPass does not interpret the regexp as such, so it is necessary
- to use <directive>ProxyPassMatch</directive> in this situation instead.</p>
-
- <p>This directive is not supported in <directive type="section" module="core"
- >Directory</directive> or <directive type="section" module="core"
- >Files</directive> sections.</p>
-
- <p>If you require a more flexible reverse-proxy configuration, see the
- <directive module="mod_rewrite">RewriteRule</directive> directive with the
- <code>[P]</code> flag.</p>
-
<p>The optional <var>interpolate</var> keyword, in combination with
<directive>ProxyPassInterpolateEnv</directive>, causes the ProxyPass
to interpolate environment variables, using the syntax
projects / thirdparty / apache / httpd.git / commitdiff
