Re: Re: why do we not set http 500 for errors when the display_error is enabled

From: Date: Wed, 25 Jun 2014 14:50:34 +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-75074@lists.php.net to get a copy of this message
On 25 June 2014 15:32, Rowan Collins <rowan.collins@gmail.com> wrote: > Chris Wright wrote (on 25/06/2014): > >> 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. > > > Internet Explorer's "friendly error messages" are shown in preference to any > content smaller than a certain number of bytes (I can't remember the exact > threshold, but you will find plenty of minimal error pages padded out with > garbage comments as a workaround). > > I've just had a quick look around online, and can't see anything saying that > this "feature" was removed in more recent versions. In fact, I just did a > quick test in IE11, and a page returning HTTP 500 and containing the text > "Done." is indeed replaced with the default error page. :( I tested briefly on my machine before sending the previous mail, but it looks like I have the option set as outlined in the KB article Ferenc linked - sorry for the misinformation. Given this apparent variation/unpredictability, having another ini setting to control the behaviour is possibly not a bad idea?

« previous php.internals (#75074) next »