diff options
author | Eric Covener <covener@apache.org> | 2014-12-20 17:07:56 +0100 |
---|---|---|
committer | Eric Covener <covener@apache.org> | 2014-12-20 17:07:56 +0100 |
commit | 094226f0cf5213ef49dd368a16d22578ac85d77a (patch) | |
tree | 1fcad6541913134fc8c9c287e68bbfc9ff77534e /docs/manual/mod/mod_proxy_fcgi.html.en | |
parent | PATH_INFO is set for free when we use SetHandler style configuration, (diff) | |
download | apache2-094226f0cf5213ef49dd368a16d22578ac85d77a.tar.xz apache2-094226f0cf5213ef49dd368a16d22578ac85d77a.zip |
xforms
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1647013 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to '')
-rw-r--r-- | docs/manual/mod/mod_proxy_fcgi.html.en | 14 |
1 files changed, 10 insertions, 4 deletions
diff --git a/docs/manual/mod/mod_proxy_fcgi.html.en b/docs/manual/mod/mod_proxy_fcgi.html.en index 7e141cf552..70d27d737c 100644 --- a/docs/manual/mod/mod_proxy_fcgi.html.en +++ b/docs/manual/mod/mod_proxy_fcgi.html.en @@ -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/" </FilesMatch> + # 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. + <Proxy fcgi://localhost/ enablereuse=on max=10> + </Proxy> <FilesMatch ...> 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 |