# Defining a worker will improve performance
# And in this case, re-use the worker (dependent on support from the fcgi application)
# If you have enough idle workers, this would only improve the performance marginally
<Proxy "fcgi://localhost:9000/" enablereuse=on max=10>
</Proxy>
<FilesMatch "\.php$">
<If "-f %{REQUEST_FILENAME}">
# Pick one of the following approaches
# Use the standard TCP socket
#SetHandler "proxy:fcgi://localhost/:9000"
# If your version of httpd is 2.4.9 or newer (or has the back-ported feature), you can use the unix domain socket
#SetHandler "proxy:unix:/path/to/app.sock|fcgi://localhost/"
</If>
</FilesMatch>
<Proxy "fcgi://localhost/" enablereuse=on max=10>
In the appropriate SetHandler invocation the target for the "fcgi://" scheme is pretty much a no nevermind and makes no difference, as I've discovered from experimentation and found mentioned in several places. What should be used for "fcgi://" in the <Proxy> directive? Or does it matter, as it doesn't for SetHandler?