ID: 50921
User updated by: phpbug at starurl dot com
Reported By: phpbug at starurl dot com
Status: Bogus
Bug Type: HTTP related
Operating System: Windows IIS6
PHP Version: 5.2.12
New Comment:
Thank you for the swift response Jani.
I can confirm that the 500 status code works for the following (runtime
error):
<?
ini_set('display_errors', 0);
$x = y();
?>
But fails for parse errors (because the "disply_errors" line doesn't
get executed):
<?
ini_set('display_errors', 0);
x = y;
?>
Firstly, is this dependency really necessary? Just because we have
'display_errors' enabled doesn't mean we want fatal errors to go
unlogged and unnoticed because a "200 OK" status is incorrectly
returned.
Secondly, the majority of PHP developers out there use shared hosting,
on which 'display_errors' is normally true and is impossible to change
globally - are we saying they're stuck with incorrect HTTP status codes
when parse errors occur?
The restriction that headers must not already have been sent is of
course understandable as it is unavoidable. Not overriding an explicitly
set HTTP status code also makes sense.
But why not set the status code as "500 Internal Server Error" when any
fatal parse/runtime error occurs, regardless of the value of
'display_errors'? This would be consistent with the HTTP spec, which
recommends a 5XX response if an error occurs, and is followed by just
about every other web server language out there (e.g., ASP, .NET).
Many thanks, BJ
Previous Comments:
------------------------------------------------------------------------
[2010-02-03 10:06:27] j...@php.net
It does happen. It requires that:
1) display_errors = off
2) No headers have been sent yet by the time the error happens
3) Status is 200 at that time.
------------------------------------------------------------------------
[2010-02-03 04:23:42] phpbug at starurl dot com
Description:
------------
My host runs PHP v5.2.12 (confirmed via phpversion) on IIS6 (Windows
Server, unknown version). When a PHP error occurs (parse error, runtime
error, etc), a "200 OK" HTTP status is returned, instead of the correct
"500 Internal Server Error".
This is despite claims in the change history for v5.2.4 that this issue
was fixed: "Changed error handler to send HTTP 500 instead of blank
page on PHP errors. (Dmitry, Andrei Nigmatulin)". This doesn't appear to
be the case on IIS6 (monitored remotely via HTTP Spy).
Reproduce code:
---------------
<?
x = y; // cause parse error
?>
Expected result:
----------------
Parse error mesage and "500 Internal Server Error" HTTP status code.
Actual result:
--------------
Parse error mesage and "200 OK" HTTP status code
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=50921&edit=1
