svn commit: r1647013 - /httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en

[co...@apache.org]

Author: covener
Date: Sat Dec 20 16:07:56 2014
New Revision: 1647013

URL: http://svn.apache.org/r1647013
Log:
xforms


Modified:
    httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en

Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en?rev=1647013&r1=1647012&r2=1647013&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_fcgi.html.en Sat Dec 20 16:07:56 2014
@@ -83,14 +83,14 @@
     from httpd, you can opt-in to connection reuse as shown in the following
     example:</p>
 
-    <div class="example"><h3>Single application instance, connection reuse</h3><pre class="prettyprint lang-config">ProxyPass /myapp/ fcgi://localhost:4000/ disablereuse=off</pre>
+    <div class="example"><h3>Single application instance, connection reuse</h3><pre class="prettyprint lang-config">ProxyPass /myapp/ fcgi://localhost:4000/ enablereuse=on</pre>
 </div>
 
     <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>
-    <div class="example"><h3>PHP-FPM</h3><pre class="prettyprint lang-config">ProxyPassMatch ^/myapp/.*\.php(/.*)?$ fcgi://localhost:9000/var/www/ disablereuse=off</pre>
+    <div class="example"><h3>PHP-FPM</h3><pre class="prettyprint lang-config">ProxyPassMatch ^/myapp/.*\.php(/.*)?$ fcgi://localhost:9000/var/www/ enablereuse=on</pre>
 </div>
 
     <p> The following example passes the request URI as a filesystem
@@ -130,6 +130,12 @@
     # Note: The only part that varies is /path/to/app.sock
     SetHandler  "proxy:unix:/path/to/app.sock|fcgi://localhost/"
 &lt;/FilesMatch&gt;
+   # Define a matching worker.
+   # The part that is matched to the SetHandler is the part that 
+   # follows the pipe. If you need to distinguish, "localhost; can
+   # be anything unique.
+   &lt;Proxy fcgi://localhost/ enablereuse=on max=10&gt;
+   &lt;/Proxy&gt;
 
 &lt;FilesMatch ...&gt;
     SetHandler  "proxy:fcgi://localhost:9000"
@@ -148,8 +154,8 @@
     provider:</p>
     <dl>
         <dt>proxy-fcgi-pathinfo</dt>
-        <dd>By default <code class="module"><a href="../mod/mod_proxy_fcgi.html">mod_proxy_fcgi</a></code> will neither create
-        nor export the <var>PATH_INFO</var> environment variable. This allows
+        <dd>When configured via <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>, <code class="module"><a href="../mod/mod_proxy_fcgi.html">mod_proxy_fcgi</a></code> will not
+        set the <var>PATH_INFO</var> environment variable. This allows
         the backend FCGI server to correctly determine <var>SCRIPT_NAME</var>
         and <var>Script-URI</var> and be compliant with RFC 3875 section 3.3.
         If instead you need <code class="module"><a href="../mod/mod_proxy_fcgi.html">mod_proxy_fcgi</a></code> to generate