Bug #15943 Updated: Viewing .phps Crashes with php.ini-recommended

ID: 15943 Updated by: michael.mauch@gmx.de Reported By: hz11@nyu.edu Status: Feedback Bug Type: Scripting Engine problem Operating System: FreeBSD PHP Version: 4.1.2 New Comment: I can verify that this bug is not solved as of php4-200207081200 - I'm on Linux/Intel, Apache 1.3.26. # HEAD http://127.0.0.1/~elmicha/php/phpinfo.phps 500 EOF instead of reponse status line Client-Date: Tue, 09 Jul 2002 16:32:58 GMT # GET http://127.0.0.1/~elmicha/php/phpinfo.phps >xxx <HTML> <HEAD><TITLE>An Error Occurred</TITLE></HEAD> <BODY> <H1>An Error Occurred</H1> 500 EOF instead of reponse status line </BODY> </HTML> # cat xxx # cat ~/php/phpinfo.php <? phpinfo(); ?> With "output_buffering = off", it works without problems. Previous Comments: ------------------------------------------------------------------------ [2002-06-19 11:58:01] derick@php.net Leaving the status at feedback then until you have time. ------------------------------------------------------------------------ [2002-06-19 11:52:34] hz11@nyu.edu I simply don't have time. If the timeframe for this is weeks, then no problem. If it's days, I can't promise anything. I'll do my best and also see if I can get someone to do it for me. Hans ------------------------------------------------------------------------ [2002-06-19 11:49:09] derick@php.net You really need to try this with the latest snapshot, why can't you test with it? Derick ------------------------------------------------------------------------ [2002-06-19 11:47:16] hz11@nyu.edu I'm unable to test the latest snapshot, but I can say that the problem still occurs with a fresh 4.2.1 compile from source. If output_buffering is commented out from php.ini, .phps files work fine. Hans ------------------------------------------------------------------------ [2002-06-18 17:15:07] sniper@php.net Derick meant this snapshot: http://snaps.php.net/php4-latest.tar.gz ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/15943 -- Edit this bug report at http://bugs.php.net/?id=15943&edit=1