Usability issue with LSAPI PHP
One php site that I have just showed up with blank pages and absolute zero errors in the log. I could not figure out what was going on with it.
I have LSAPI PHP 5.2.2 compiled.
So I get to the command line, and run the file in the command line using fastcgi PHP 5.2.1. No problem, the file executed perfectly.
Then I ran the same exact file with LSAPI PHP from the command line, and it brought up a bought of "can't start headers, output already started errors" immediately.
This was caused by extra white space in the config file after the closing "?>" bracket. This annoyance plagued PHP 4, but thankfully Zend fixed that problem for PHP 5. It ignores white space between the last closing bracket and EOF if there is no other characters present there.
So I have two major worries here:
1) Why is LSAPI PHP sensitive to trailing white space when CLI/CGI PHP is not?
2) Why did Litespeed return no output and not log any errors when the script was clearing outputting errors? I've seen similar behavior with litespeed when the fastcgi process died to a 500 server error. Is that is what is going on here?