From 094226f0cf5213ef49dd368a16d22578ac85d77a Mon Sep 17 00:00:00 2001
From: Eric Covener
ProxyPass /myapp/ fcgi://localhost:4000/ disablereuse=off+
ProxyPass /myapp/ fcgi://localhost:4000/ enablereuse=on
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.
-ProxyPassMatch ^/myapp/.*\.php(/.*)?$ fcgi://localhost:9000/var/www/ disablereuse=off+
ProxyPassMatch ^/myapp/.*\.php(/.*)?$ fcgi://localhost:9000/var/www/ enablereuse=on
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:
mod_proxy_fcgi
will neither create
- nor export the PATH_INFO environment variable. This allows
+ ProxyPass
or ProxyPassMatch
, mod_proxy_fcgi
will not
+ set the PATH_INFO environment variable. This allows
the backend FCGI server to correctly determine SCRIPT_NAME
and Script-URI and be compliant with RFC 3875 section 3.3.
If instead you need mod_proxy_fcgi
to generate
--
cgit v1.2.3