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

On Wed, Jun 25, 2014 at 4:32 PM, 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. :( > > we can't(and shouldn't) try to pad the response, as it could be any format, not just html. but I do think that we could expect the developer to be able to use the view source functionallity to see the "true" output when presented with the generic IE error page. and this feature of ours breaks the semantic meaning of the http response code and causes problems for those using any other browser than IE. -- Ferenc Kovács @Tyr43l - http://tyrael.hu