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/02/11 11:09:15 UTC

svn commit: r1823832 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml

Author: elukey
Date: Sun Feb 11 11:09:15 2018
New Revision: 1823832

URL: http://svn.apache.org/viewvc?rev=1823832&view=rev
Log:
mod_proxy_fcgi.xml: add more context to the conn reuse note

Modified:
    httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml

Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml?rev=1823832&r1=1823831&r2=1823832&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.xml Sun Feb 11 11:09:15 2018
@@ -89,8 +89,9 @@ ProxyPass "/myapp/" "fcgi://localhost:40
     By default mod_proxy (configured with <code>enablereuse=on</code>)
     allows a connection pool of
     <directive module="mpm_common">ThreadsPerChild</directive> connections to the
-    backend for each httpd process, so the following use cases should be taken
-    into account:</p>
+    backend for each httpd process when using a threaded mpm (like
+    <module>worker</module> or <module>event</module>),
+    so the following use cases should be taken into account:</p>
     <ul>
       <li>Under HTTP/1.1 load it will likely cause the creation of up to
       <directive module="mpm_common">MaxRequestWorkers</directive>