Commit b8afc1e8 authored by mike's avatar mike

Fixed documentation bug in FastCGI section-- '-socket' accepts only a filename,

not a path.
parent 7d0d5672
...@@ -176,10 +176,16 @@ FastCgiExternalServer /PATH/TO/apache/htdocs/zope \ ...@@ -176,10 +176,16 @@ FastCgiExternalServer /PATH/TO/apache/htdocs/zope \
...or like this for a socket configuration:: ...or like this for a socket configuration::
FastCgiIpcDir /tmp
FastCgiExternalServer /PATH/TO/apache/htdocs/zope \ FastCgiExternalServer /PATH/TO/apache/htdocs/zope \
-socket /tmp/zope.soc \ -socket zope.soc \
-pass-header Authorization -pass-header Authorization
The FastCgiIpcDir directive is needed to tell FastCGI where to find
the socket file. By default, FastCGI will look in /tmp/fcgi. You
*cannot* specify a full path with the '-socket' option, only a
filename within the FastCgiIpcDir.
The first argument after the directive name is confusing. Apache The first argument after the directive name is confusing. Apache
maps URLs to directories and files within your 'DocumentRoot'. You maps URLs to directories and files within your 'DocumentRoot'. You
must specify the name of a file within your DocumentRoot directory, must specify the name of a file within your DocumentRoot directory,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment