I believe the issue here is that PHP won't display the proper HTTP headers in the CLI version:
C:\> Php.exe test.php X-Powered-By: PHP/4.2.2 Content-type: text/html Testing 1 2 3 C:\> C:\> Php-cli.exe test.php Testing 1 2 3 C:\> >-----Original Message----- >From: Philip Olson [mailto:[EMAIL PROTECTED]] >Sent: Sunday, December 08, 2002 11:07 AM >To: Alexander Wagner >Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; >'Christoph Grottolo'; [EMAIL PROTECTED] >Subject: Re: [PHP-DEV] php.exe - php-cgi.exe > > > >Can someone provide a history of this and the problems >one will see when trying to run php.exe as a cgi (i.e. >follows one of the many install texts out there). > >This is _sorta_ documented but not really, only the >apache2 docs make any mention of it thus far. > >Regards, >Philip > > >On Sun, 8 Dec 2002, Alexander Wagner wrote: > >> On Sunday 08 December 2002 01:02, John Coggeshall wrote: >> > I think a big ole' message at the end of ./configure will >> > drastically reduce the number of problems. >> >> With php.exe? *g* >> >> > Also, perhaps a check could be put in the >> > CLI version of PHP that would throw an error message if it >is being >> > used as a CGI... >> >> A _meaningful_ error-message in the right place would be the right >> thing (tm). >> Too many people don't read release-notes. >> >> regards >> Wagner >> >> -- >> codito ergo sum >> >> -- >> PHP Development Mailing List <http://www.php.net/> >> To unsubscribe, visit: http://www.php.net/unsub.php >> > > > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
