Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75071 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87390 invoked from network); 25 Jun 2014 14:32:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jun 2014 14:32:14 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.175 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.216.175 mail-qc0-f175.google.com Received: from [209.85.216.175] ([209.85.216.175:40682] helo=mail-qc0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 38/A3-55756-C6DDAA35 for ; Wed, 25 Jun 2014 10:32:13 -0400 Received: by mail-qc0-f175.google.com with SMTP id i8so1756789qcq.20 for ; Wed, 25 Jun 2014 07:32:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Dj93Dr4LmJCT2hza4YUn/liTggP6xb6FXut5ya9fwGo=; b=ca/Rb+YnpuEpsiVwB0ZEUKjWNC04YqE7E/x4PuBA44fu1chOISP0cFzjIpotRZxPNg kJNGQZ7cJTLxwF05FipNslV5oycE1A0CvYeGBBNS4jSRtOnGawmeaEkUA3iar3tTv5v6 KpzIcUSkyrbsFYc9Av8s9fytqBMmd2Cen1CC3aM6rKfcAJdhbLPfYDsWedM2f8Gd0Z1O rKsMt32DJfQWUKJ7v+Lqw1nq4vo7I2WtfFP50qAEUrsulmgAOGyRiovgrLngZktJuj6T vHN7IDkJkdSRbTGq+p27IylMzzT7lruYGDUI8yvXYbJscJKZJlGVLKT/h+TjJHvXh4ky BUiw== MIME-Version: 1.0 X-Received: by 10.229.103.130 with SMTP id k2mr12323147qco.1.1403706730532; Wed, 25 Jun 2014 07:32:10 -0700 (PDT) Received: by 10.140.25.36 with HTTP; Wed, 25 Jun 2014 07:32:10 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 Jun 2014 16:32:10 +0200 Message-ID: To: Dmitry Stogov Cc: PHP Internals , Dmitry Stogov Content-Type: multipart/alternative; boundary=001a1133453c0ad6e104fca9f1eb Subject: Re: why do we not set http 500 for errors when the display_error is enabled From: tyra3l@gmail.com (Ferenc Kovacs) --001a1133453c0ad6e104fca9f1eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Jun 25, 2014 at 3:30 PM, Dmitry Stogov wrote: > We can't set 500 response code if HTTP headers were already sent. > we have the !SG(headers_sent) check for that, and I'm not proposing to remove that(albeit I think that we could handle the special scenario, when the only output is generated by the error, but that is a separate topic). > > 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 jus= t > IE6 or below and it's not a problem anymore). > 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. thanks for the explanation! --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --001a1133453c0ad6e104fca9f1eb--