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 2017/07/28 09:29:46 UTC
svn commit: r1803259 - in /httpd/httpd/branches/2.4.x/docs/manual:
mod/mod_proxy.html.en mod/mod_proxy_fcgi.html.en rewrite/flags.html.en
Author: elukey
Date: Fri Jul 28 09:29:46 2017
New Revision: 1803259
URL: http://svn.apache.org/viewvc?rev=1803259&view=rev
Log:
Documentation rebuild
Modified:
httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.html.en
httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy_fcgi.html.en
httpd/httpd/branches/2.4.x/docs/manual/rewrite/flags.html.en
Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.html.en?rev=1803259&r1=1803258&r2=1803259&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.html.en (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy.html.en Fri Jul 28 09:29:46 2017
@@ -244,7 +244,7 @@ ProxyVia On
<p>The two default workers have a fixed configuration
and will be used if no other worker matches the request.
- They do not use HTTP Keep-Alive or connection pooling.
+ They do not use HTTP Keep-Alive or connection reuse.
The TCP connections to the origin server will instead be
opened and closed for each request.</p>
@@ -344,8 +344,8 @@ ProxyPass "/examples" "http://backend.ex
<div class="note"><h3>DNS resolution for origin domains</h3>
<p>DNS resolution happens when the socket to
the origin domain is created for the first time.
- When connection pooling is used, each backend domain is resolved
- only once per child process, and reused for all further connections
+ When connection reuse is enabled, each backend domain is resolved
+ only once per child process, and cached for all further connections
until the child is recycled. This information should to be considered
while planning DNS maintenance tasks involving backend domains.
Please also check <code class="directive"><a href="#proxypass">ProxyPass</a></code>
@@ -990,7 +990,11 @@ through</td></tr>
a local virtual path; <var>url</var> is a partial URL for the
remote server and cannot include a query string.</p>
- <div class="note"><strong>Note: </strong>This directive is not supported within
+ <div class="note">It is strongly suggested to review the concept of a
+ <a href="#workers">Worker</a> before proceeding any further
+ with this section.</div>
+
+ <div class="note">This directive is not supported within
<code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> and
<code class="directive"><a href="../mod/core.html#files"><Files></a></code> containers.</div>
@@ -1097,24 +1101,26 @@ ProxyPass "/mirror/foo" "http://backend.
using <code>key=value</code> parameters, described in the tables
below.</p>
+ <div class="warning"><h3>Maximum connections to the backend</h3>
<p>By default, mod_proxy will allow and retain the maximum number of
connections that could be used simultaneously by that web server child
process. Use the <code>max</code> parameter to reduce the number from
- the default. Use the <code>ttl</code> parameter to set an optional
+ the default. The pool of connections is maintained per web server child
+ process, and <code>max</code> and other settings are not coordinated
+ among all child processes, except when only one child process is allowed
+ by configuration or MPM design.</p>
+ </div>
+
+ <p>Use the <code>ttl</code> parameter to set an optional
time to live; connections which have been unused for at least
<code>ttl</code> seconds will be closed. <code>ttl</code> can be used
to avoid using a connection which is subject to closing because of the
backend server's keep-alive timeout.</p>
- <p>The pool of connections is maintained per web server child
- process, and <code>max</code> and other settings are not coordinated
- among all child processes, except when only one child process is allowed
- by configuration or MPM design.</p>
-
<div class="example"><h3>Example</h3><pre class="prettyprint lang-config">ProxyPass "/example" "http://backend.example.com" max=20 ttl=120 retry=300</pre>
</div>
- <table class="bordered"><tr><th>BalancerMember parameters</th></tr></table>
+ <table class="bordered"><tr><th>Worker|BalancerMember parameters</th></tr></table>
<table>
<tr><th>Parameter</th>
<th>Default</th>
@@ -1165,7 +1171,10 @@ ProxyPass "/mirror/foo" "http://backend.
httpd and
the backend server (regardless of protocol) tends to silently
drop connections or when backends themselves may be under round-
- robin DNS. To disable connection pooling reuse,
+ robin DNS.
+ When connection reuse is enabled each backend domain is resolved
+ (with a DNS query) only once per child process and cached for all further
+ connections until the child is recycled. To disable connection reuse,
set this property value to <code>On</code>.
</td></tr>
<tr><td>enablereuse</td>
Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy_fcgi.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy_fcgi.html.en?rev=1803259&r1=1803258&r2=1803259&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy_fcgi.html.en (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_proxy_fcgi.html.en Fri Jul 28 09:29:46 2017
@@ -95,7 +95,7 @@
<p> The following example passes the request URI as a filesystem
path for the PHP-FPM daemon to run. The request URL is implicitly added
to the 2nd parameter. The hostname and port following fcgi:// are where
- PHP-FPM is listening. Connection pooling is enabled.</p>
+ PHP-FPM is listening. Connection pooling/reuse is enabled.</p>
<div class="example"><h3>PHP-FPM</h3><pre class="prettyprint lang-config">ProxyPassMatch "^/myapp/.*\.php(/.*)?$" "fcgi://localhost:9000/var/www/" enablereuse=on</pre>
</div>
Modified: httpd/httpd/branches/2.4.x/docs/manual/rewrite/flags.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/rewrite/flags.html.en?rev=1803259&r1=1803258&r2=1803259&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/rewrite/flags.html.en (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/rewrite/flags.html.en Fri Jul 28 09:29:46 2017
@@ -536,7 +536,7 @@ client undue influence.</p>
<p>Using this flag triggers the use of <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code>, without handling of persistent connections. This
means the performance of your proxy will be better if you set it up with <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> or
<code class="directive"><a href="../mod/mod_proxy.html#proxypassmatch">ProxyPassMatch</a></code></p>
-<p>This is because this flag triggers the use of the default worker, which does not handle connection pooling.</p>
+<p>This is because this flag triggers the use of the default worker, which does not handle connection pooling/reuse.</p>
<p>Avoid using this flag and prefer those directives, whenever you can.</p>
</div>