ID:               42722
 Updated by:       [EMAIL PROTECTED]
 Reported By:      mabismad at msn dot com
-Status:           Assigned
+Status:           Feedback
 Bug Type:         *General Issues
 Operating System: WinXP
 PHP Version:      5.2.4
 Assigned To:      dmitry
 New Comment:

I cannot reproduce it with CVS version.

$ sapi/cgi/php-cgi -d display_errors=0 -d error_reporting=E_ALL
wrong.php
Status: 500 Internal Server Error
X-Powered-By: PHP/5.3.0-dev
Content-type: text/html

$ sapi/cgi/php-cgi -d display_errors=1 -d error_reporting=E_ALL
wrong.php
X-Powered-By: PHP/5.3.0-dev
Content-type: text/html

<br />
<b>Parse error</b>:  syntax error, unexpected T_STRING in
<b>/home/dmitry/php/php5.3/CGI-DEBUG/x.php</b> on line <b>2</b><br />
/home/dmitry/php/php5.3/CGI-DEBUG/wrong.php(2) : Parse error - syntax
error, unexpected T_STRING



Previous Comments:
------------------------------------------------------------------------

[2007-09-30 21:37:28] [EMAIL PROTECTED]

Dmitry, please check this out.

------------------------------------------------------------------------

[2007-09-21 02:22:49] mabismad at msn dot com

Description:
------------
The display errors and error reporting change to accomplish the
following - "Changed error handler to send HTTP 500 instead of blank
page on PHP errors. (Dmitry, Andrei Nigmatulin)" - apparently does not
check if there is actual output due to the display errors/error
reporting settings.

When display_errors is set to On and error_reporting is set to E_ALL,
only Notice and Warning level messages are output to the browser. Fatal
parse errors (and probably other types) unconditionally cause a HTTP 500
page.

The HTTP 500 redirect should only occur when there is absolutely no
actual output from any of the display errors/error reporting settings.



------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=42722&edit=1

Reply via email to