Loading docs/manual/mod/mod_proxy.xml +20 −16 Original line number Diff line number Diff line Loading @@ -756,6 +756,22 @@ expressions</description> </p> </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>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 <code>!</code> directive is useful in situations where you don't want to reverse-proxy a subdirectory, <em>e.g.</em></p> Loading Loading @@ -783,6 +799,8 @@ expressions</description> </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 Loading Loading @@ -1071,6 +1089,8 @@ expressions</description> </Proxy> </example> <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> Loading @@ -1079,22 +1099,6 @@ expressions</description> as it removes the normal limited protection against URL-based attacks provided by the proxy.</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 (available in httpd 2.2.9 and later), in combination with <directive>ProxyPassInterpolateEnv</directive>, causes the ProxyPass Loading Loading
docs/manual/mod/mod_proxy.xml +20 −16 Original line number Diff line number Diff line Loading @@ -756,6 +756,22 @@ expressions</description> </p> </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>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 <code>!</code> directive is useful in situations where you don't want to reverse-proxy a subdirectory, <em>e.g.</em></p> Loading Loading @@ -783,6 +799,8 @@ expressions</description> </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 Loading Loading @@ -1071,6 +1089,8 @@ expressions</description> </Proxy> </example> <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> Loading @@ -1079,22 +1099,6 @@ expressions</description> as it removes the normal limited protection against URL-based attacks provided by the proxy.</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 (available in httpd 2.2.9 and later), in combination with <directive>ProxyPassInterpolateEnv</directive>, causes the ProxyPass Loading