Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75073
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53AADD67.309@gmail.com>
References: <CAH-PCH6EZBhoYXNk8z_LP7AGxSjiVQVrZeQ2VhwmXuCp4C3ySA@mail.gmail.com>
	<CA+9eiLuM2VfYssk0z7KEqffoh8fwZ1bNR+bFFtTviKa_UMWhZQ@mail.gmail.com>
	<CAGAGxbYaN+ymyPaJ=k1VhF-O9fAUY3C3-Rh5jG6sEpkXY_tK9A@mail.gmail.com>
	<53AADD67.309@gmail.com>
Date: Wed, 25 Jun 2014 16:49:46 +0200
Message-ID: <CAH-PCH4z7ZtTEgT3ssE9LMOUyqePAW56WqmfpAG+gYGR+xN8Cw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c2acc8f9816204fcaa2f3f
Subject: Re: [PHP-DEV] Re: why do we not set http 500 for errors when the
 display_error is enabled
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a11c2acc8f9816204fcaa2f3f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 o=
ut
> 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 th=
e
> 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.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a11c2acc8f9816204fcaa2f3f--