Edit report at https://bugs.php.net/bug.php?id=50921&edit=1
ID: 50921
Comment by: robberphex at gmail dot com
Reported by: phpbug at starurl dot com
Summary: '200 OK' HTTP status despite PHP error
Status: Re-Opened
Type: Bug
Package: HTTP related
Operating System: *
PHP Version: 5.2.12
Block user comment: N
Private report: N
New Comment:
I'm trying to fix this.
Please review https://github.com/php/php-src/pull/3244.
And, Xdebug have same bug. If you are interested, see https://github.com/xdebug/xdebug/pull/420
Previous Comments:
------------------------------------------------------------------------
[2018-05-05 18:01:18] requinix@php.net
Related To: Bug #36636
------------------------------------------------------------------------
[2017-11-06 21:19:46] chealer at gmail dot com
I still experience this with XAMPP 5.6.30's PHP 5.6.30.
------------------------------------------------------------------------
[2017-10-06 13:21:05] antoine dot gilabert at gmail dot com
i've done this to solve the problem:
register_shutdown_function( "fatal_handler" );
function fatal_handler() {
http_response_code (500);
}
------------------------------------------------------------------------
[2016-07-12 18:05:00] chealer at gmail dot com
I am experiencing this symptom under WampServer 2.5, which uses PHP 5.5.12. This happens even after
disabling Xdebug, and even though display_errors is set to On. Is this caused by the same bug?
I agree with jonathan, josh and xmeltrut; a preference could be introduced, but the default behavior
should not be the current behavior.
------------------------------------------------------------------------
[2015-12-14 17:31:59] josh dot ribakoff at gmail dot com
Yes, just because 1% of programmers may be using ob_flush() doesn't mean the other 99% are.
Most PHP frameworks (Zend, Symfony, Silex) use some sort of controller that returns a response at
the end of the request only. Specifically this is a big issue for ajax, which I'm pretty sure
is impossible to use ob_flush() with, seeing as you need to build up a full response & output it
at the end with json_encode() in its entirety.
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=50921
--
Edit this bug report at https://bugs.php.net/bug.php?id=50921&edit=1