Req #41342 [Com]: PHP says syntax errors are 200 OK

Edit report at https://bugs.php.net/bug.php?id=41342&edit=1 ID: 41342 Comment by: bjoerndietz at gmx dot de Reported by: defenestrator at gmail dot com Summary: PHP says syntax errors are 200 OK Status: Not a bug Type: Feature/Change Request Package: Feature/Change Request Operating System: FreeBSD PHP Version: 5.2.2 Block user comment: N Private report: N New Comment: I'm not sure if this is good practise or not, but many php-based webservices use the HTTP response codes to declare if the process invoked has been successful or not. For those it can be a painful experience looking for a possible error behaviour while only dealing with the 200 response (yes, the clients should look at the additional data returned if there are any). Therefore there should be some way to configure the HTTP response code for these situations. I'd expect a 500 error, too. Previous Comments: ------------------------------------------------------------------------ [2010-02-08 02:36:16] defenestrator at gmail dot com Having display_errors off should not be part of the correct conditions. I have display_errors on in my development environment, and I want a 500 code in that situation. Getting a 200 code causes errors to be cached, and if there's such an error in an AJAX request, then it can't be easily refreshed in some browsers. I have to test things in a lot of browsers, so it would be great if I could get a 500 here. ------------------------------------------------------------------------ [2010-02-03 10:04:23] jani@php.net Already happens in correct conditions. (display_errors off, headers not sent by the time error happens and if status was 200 before the error) ------------------------------------------------------------------------ [2009-08-27 11:55:16] steffen at steffen-gebert dot de I have display_errors off and I also get code 200 (on syntax errors, undefined functions, ..). Please.. really sent 500 here! ------------------------------------------------------------------------ [2009-03-17 18:45:53] php at plummer dot us I just want to be able to notify people of errors. With syntax errors, I can't use php code to do so and the web server doesn't know there's been a problem when a 200 response is returned so I can't use its error reporting capabilities. Basically it violates the http rfc to return a 200 on an error response. ------------------------------------------------------------------------ [2008-11-30 00:02:19] defenestrator at gmail dot com I need display_errors on in development environments, which is where the 200 OK response is causing the inconvenience for me in the first place. If I make an AJAX request to a PHP file that produces an error, then I can correct the error but any further requests to the same URL are pulled out of the browser cache, with no direct way to refresh it. Many workarounds exist but none should be necessary. There really isn't any benefit to *not* producing a 500 error here. ------------------------------------------------------------------------ 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=41342 -- Edit this bug report at https://bugs.php.net/bug.php?id=41342&edit=1