[jrmarino]

You may have misunderstood the problem of number 1. I'm talking about the white space between the end of the script and the end of the file. for example:

<php

/* do stuff */

?>


(See this white space?  This is ignored by CLI/CGI PHP.  It is NOT ignored LSAPI PHP and it gets sent to stdout)
[EOF]

Both the fastcgi and lsapi PHP were compiled from the same source. The one thing that might explain this: fastcgi php looks at the php.ini in the default location. If lsapi does not, it could explain some of these differences.

2) I accept that litespeed may have interpreted the entire page as a header. I still don't know why an error was not logged. I'm also repeating: the output between lsapi PHP and fastcgi php running on the command line was not equal due to the differently handling of the trailing white space.


I can imagine some php.ini setting that handles trailing white space, but that means lsapi and fastcgi php are not using the same php.ini file.