Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75070
Return-Path: <are.you.winning@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 84164 invoked from network); 25 Jun 2014 13:46:26 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 25 Jun 2014 13:46:26 -0000
Authentication-Results: pb1.pair.com smtp.mail=are.you.winning@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=are.you.winning@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.169 as permitted sender)
X-PHP-List-Original-Sender: are.you.winning@gmail.com
X-Host-Fingerprint: 209.85.216.169 mail-qc0-f169.google.com  
Received: from [209.85.216.169] ([209.85.216.169:59210] helo=mail-qc0-f169.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 8B/33-55756-1B2DAA35 for <internals@lists.php.net>; Wed, 25 Jun 2014 09:46:25 -0400
Received: by mail-qc0-f169.google.com with SMTP id c9so1720797qcz.28
        for <internals@lists.php.net>; Wed, 25 Jun 2014 06:46:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:cc:content-type;
        bh=Ad8k5Y4de6Ri1BwfsMPRmVxUWAJl4kBeH1fUxiakm8k=;
        b=DGRatWPHwedirdqxU3lXR4gtYklHbfb5vdI9aknddFbXiSaJCwOnYO7jKNieGm/YnK
         uTNrgukWtE7bpJiEnxOZKF2YY2WBYtOvGi60HJUwleNad/tHJTqkmUitbkhD7mj8fcJW
         ynYU5dXdoLmxK/AAMTvuOD+R0H8RKLyDBMq1OKreymmDOT9JI9O5HFScQml8HaJGLEsw
         t5pGNIVt1o7GdWYcyULFUHVohgKX7chnvXYgmDY86F7uEp1jaIvMdes7fBsO+wYpMn6y
         2587pk5wAl7lis/JsQZkkFr0sf3ESwKytwLU6MPTYxhZQVjrDlFGUs031Aiy10ok84QH
         Nuew==
MIME-Version: 1.0
X-Received: by 10.140.93.163 with SMTP id d32mr11645736qge.1.1403703982562;
 Wed, 25 Jun 2014 06:46:22 -0700 (PDT)
Sender: are.you.winning@gmail.com
Received: by 10.229.149.73 with HTTP; Wed, 25 Jun 2014 06:46:22 -0700 (PDT)
In-Reply-To: <CA+9eiLuM2VfYssk0z7KEqffoh8fwZ1bNR+bFFtTviKa_UMWhZQ@mail.gmail.com>
References: <CAH-PCH6EZBhoYXNk8z_LP7AGxSjiVQVrZeQ2VhwmXuCp4C3ySA@mail.gmail.com>
	<CA+9eiLuM2VfYssk0z7KEqffoh8fwZ1bNR+bFFtTviKa_UMWhZQ@mail.gmail.com>
Date: Wed, 25 Jun 2014 14:46:22 +0100
X-Google-Sender-Auth: FSObYew_bUoUn8fu8-7-XVXclEc
Message-ID: <CAGAGxbYaN+ymyPaJ=k1VhF-O9fAUY3C3-Rh5jG6sEpkXY_tK9A@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: Ferenc Kovacs <tyra3l@gmail.com>, PHP Internals <internals@lists.php.net>, 
	Dmitry Stogov <dmitry@php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Re: why do we not set http 500 for errors when the
 display_error is enabled
From: cw@daverandom.com (Chris Wright)

On 25 June 2014 14:30, Dmitry Stogov <dmitry@zend.com> wrote:
> We also don't set 500 response code if display_error is "on", because
> browsers won't show the actual page with error message (may be it was just
> IE6 or below and it's not a problem anymore).

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.

If people are worried that this element, another ini setting could
always be introduced to control the behaviour separately from
display_errors.