This module requires the service of mod_proxy. It provides support for the
FastCGI protocol.
Thus, in order to get the ability of handling the FastCGI
protocol, mod_proxy and
mod_proxy_fcgi have to be present in the server.
Unlike mod_fcgid
and mod_fastcgi,
mod_proxy_fcgi has no provision for starting the
application process; fcgistarter is provided for
that purpose.
Warning
Do not enable proxying until you have secured your server. Open proxy
servers are dangerous both to your network and to the Internet at
large.
Examples
Remember, in order to make the following examples work, you have to
enable mod_proxy and mod_proxy_fcgi.
Single application instance
ProxyPass /myapp/ fcgi://localhost:4000/
This application should be able to handle multiple concurrent
connections. mod_proxy enables connection reuse by
default, so after a request has been completed the connection will be
held open by that httpd child process and won't be reused until that
httpd process routes another request to the application. If the
FastCGI application is unable to handle enough concurrent connections
from httpd, requests can block waiting for the application to close
an existing connection. One way to resolve this is to disable connection
reuse on the ProxyPass directive, as shown in
the following example:
Single application instance, no connection reuse
ProxyPass /myapp/ fcgi://localhost:4000/ disablereuse=on
The balanced gateway needs mod_proxy_balancer and
at least one load balancer algorithm module, such as
mod_lbmethod_byrequests, in addition to the proxy
modules listed above. mod_lbmethod_byrequests is the
default, and will be used for this example configuration.
Balanced gateway to multiple application instances
ProxyPass /myapp/ balancer://myappcluster/
<Proxy balancer://myappcluster/>
BalancerMember fcgi://localhost:4000/
BalancerMember fcgi://localhost:4001/
</Proxy>