Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75080
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53AAFF9B.1020005@anderiasch.de>
References: <CAH-PCH6EZBhoYXNk8z_LP7AGxSjiVQVrZeQ2VhwmXuCp4C3ySA@mail.gmail.com>
	<CA+9eiLuM2VfYssk0z7KEqffoh8fwZ1bNR+bFFtTviKa_UMWhZQ@mail.gmail.com>
	<CAH-PCH4=PmhLzbQYRwZBx=XZWZSw7TKiGaGstdKjyqf2bcL=0Q@mail.gmail.com>
	<C796C08E-87F8-425E-9236-F85CF427A1C2@ajf.me>
	<53AAED25.30509@gmail.com>
	<53AAFF9B.1020005@anderiasch.de>
Date: Wed, 25 Jun 2014 19:52:12 +0200
Message-ID: <CAH-PCH4Od4viKz5mCS1QonBCTTeUd5Wa1zgybVKyKk+hLnN=SQ@mail.gmail.com>
To: Florian Anderiasch <ml@anderiasch.de>
Cc: Rowan Collins <rowan.collins@gmail.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c14a7c6fa5eb04fcacbce2
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)

--001a11c14a7c6fa5eb04fcacbce2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 25, 2014 at 6:58 PM, Florian Anderiasch <ml@anderiasch.de>
wrote:

> On 25.06.2014 17:39, Rowan Collins wrote:
> > Andrea Faulds wrote (on 25/06/2014):
> >> 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=E2=80=99t other browsers do this as well? I believe Chrome and Fir=
efox do,
> >> at least for 404 errors.
> >
> > Firefox and Chrome only show the default message if the response length
> > is ZERO bytes. Even the 26-byte response generated by empty content
> > going through gzip buffering appears to be enough for them both to show
> > the "real" output (in that case, a blank page).
> >
> > So it really is just IE that has this notion of the error message havin=
g
> > to be "long enough".
>
> It might be cache settings, but my Chromium definitely does not show a
> "default message" if I get a 204 with zero bytes, it keeps displaying
> the old content (if the url is the same). Developer Tools of course show
> this, but not the actual contents of the browser tab.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
that is a special case, and that is how it should be handled:
http://www.ietf.org/rfc/rfc2616.txt

   If the client is a user agent, it SHOULD NOT change its document view
   from that which caused the request to be sent. This response is
   primarily intended to allow input for actions to take place without
   causing a change to the user agent's active document view, although
   any new or updated metainformation SHOULD be applied to the document
   currently in the user agent's active view.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a11c14a7c6fa5eb04fcacbce2--