</Proxy></pre>
</div>
- <div class="example"><h3>Proxy via Handler</h3><p>You can also force a request to be handled as a reverse-proxy
+ <p>You can also force a request to be handled as a reverse-proxy
request, by creating a suitable Handler pass-through. The example
configuration below will pass all requests for PHP scripts to the
- specified FastCGI server using reverse proxy:
- </p><pre class="prettyprint lang-config"><FilesMatch \.php$>
+ specified FastCGI server using reverse proxy.
+ This feature is available in Apache HTTP Server 2.4.10 and later. For performance
+ reasons, you will want to define a <a href="../mod_proxy.html#worker">worker</a>
+ representing the same fcgi:// backend. The benefit of this form is that it
+ allows the normal mapping of URI to filename to occur in the server, and the
+ local filesystem result is passed to the backend.
+ </p>
+ <div class="example"><h3>Proxy via Handler</h3><pre class="prettyprint lang-config"><FilesMatch \.php$>
SetHandler "proxy:unix:/path/to/app.sock|fcgi://localhost/"
</FilesMatch></pre>
-<p>This feature is available in Apache HTTP Server 2.4.10 and later. For performance
- reasons, you will want to define a <a href="../mod_proxy.html#worker">worker</a>
- representing the same fcgi:// backend.</p></div>
+</div>
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="env" id="env">Environment Variables</a></h2>