From: Sascha Schumann Date: Wed, 3 Sep 2003 08:24:37 +0000 (+0000) Subject: Update documentation, -b ip:port works X-Git-Tag: RELEASE_0_7~269 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=dcd0b8fc9094b1baa523932266b37557485f9c99;p=php Update documentation, -b ip:port works --- diff --git a/sapi/cgi/README.FastCGI b/sapi/cgi/README.FastCGI index 9e5d4ae97b..c2952c0768 100644 --- a/sapi/cgi/README.FastCGI +++ b/sapi/cgi/README.FastCGI @@ -25,13 +25,22 @@ or may not be as efficient. In this setup, PHP is started as a separate process entirely from the web server. It will listen on a socket for new FastCGI requests, and deliver PHP pages as appropriate. This is the recommended way of running PHP-FastCGI. -To run this way, you must start the PHP binary running by giving it a port -number to listen to on the command line, e.g.: +To run this way, you must start the PHP binary running by giving it an IP +and a port number to listen to on the command line, e.g.: -./php -b 8002 + ./php -b 127.0.0.1:8002 -(you can also specify a bind address, e.g. ./php -b localhost:8002. However, this - relies on the FastCGI devkit and does not seem to work properly) +The above line is the recommended way of running FastCGI. You usually +want the FastCGI server to provide services to the localhost, not +everyone on the Internet. + +If your web server sits on a remote host, you can make FastCGI listen +on all interfaces: + + ./php -b :8002 + ./php -b "*:8002" + +Note that hostnames are not supported. You must also configure your web server to connect to the appropriate port in order to talk to the PHP FastCGI process.