Re: Re: why do we not set http 500 for errors when the display_error is enabled
| From: | Ferenc Kovacs | Date: | Wed, 25 Jun 2014 15:31:43 +0000 |
| Subject: | Re: Re: why do we not set http 500 for errors when the display_error is enabled | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-75077@lists.php.net to get a copy of this message | ||
On Wed, Jun 25, 2014 at 4:55 PM, Andrea Faulds <ajf@ajf.me> wrote:
>
> On 25 Jun 2014, at 15:32, Ferenc Kovacs <tyra3l@gmail.com> wrote:
>
> > I see. I assume this is related to
> http://support.microsoft.com/kb/294807
> > where by default IE shows pretty but generic message for non-2xx messages
> > if the response content length is less than or equal to a specific
> > threshold(512 bytes for 500 errors for example).
> > I don't think that it was a good idea to patch our error handling for the
> > sake of an usability feature only present in one browser.
>
> Don’t other browsers do this as well? I believe Chrome and Firefox do, at
> least for 404 errors.
>
I could only check chrome, safari and firefox on my mac, but all of those
properly show the expected output(123) for
<?php
header('HTTP/1.1 500 Internal Server Error');
echo "123";
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu