Re: Re: why do we not set http 500 for errors when the display_error is enabled
| From: | Chris Wright | Date: | Wed, 25 Jun 2014 13:46:22 +0000 |
| Subject: | Re: Re: why do we not set http 500 for errors when the display_error is enabled | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-75070@lists.php.net to get a copy of this message | ||
On 25 June 2014 14:30, Dmitry Stogov <dmitry@zend.com> wrote:
> We also don't set 500 response code if display_error is "on", because
> browsers won't show the actual page with error message (may be it was just
> IE6 or below and it's not a problem anymore).
I don't believe this is the case with any browser we might still be
reasonably expected to support. The browser generic error pages are
only displayed when there is no body content or a content-type it
doesn't understand.
If people are worried that this element, another ini setting could
always be introduced to control the behaviour separately from
display_errors.