Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96526
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.15 as permitted sender)
To: Stephen Reay <php-lists@koalephant.com>, Yasuo Ohgaki <yohgaki@php.net>
References: <CAGa2bXb0CKP6=eZZk2atR5XGtR8JmQ3FG756wn0J7kkPGYFyZg@mail.gmail.com>
 <1eab7492-596c-ffd2-81ed-0eb9256a033e@gmail.com>
 <CAGa2bXY5u_VgJnoOq06dGj4uS2uVDwCC4qm358tJHEq+gfHVuw@mail.gmail.com>
 <0B722A15-A29F-498B-987F-F6BA5AA49EEF@bobs-bits.com>
 <CAGa2bXZq6uydypJNGw3n7wJ3VRCS0o3c2L_FABYJZ-B1x4naGg@mail.gmail.com>
 <59D6B40B-DC64-43A3-AED4-CD5C9C15B6BA@koalephant.com>
 <CAGa2bXbVMvkUsHvsjJ7YVO6pY84rV1RTcG0PzusdK8a+ff9C0g@mail.gmail.com>
 <CANUQDCg6FAiOFpyoaq2EyPjxrLGN+4XzXdf7fX66yVbAR9Q2EA@mail.gmail.com>
 <CAGa2bXZrO2SiqPV6wDb=3+9XGdNHFUSPL5Qoh4yR-_Hq62GyVw@mail.gmail.com>
 <CANUQDCiJcaX4mbbcgCjZFtCFxzCMSjjLN-h6gtyyX1d_HVdBKw@mail.gmail.com>
 <A9816C1C-70F4-49E0-93D8-FE370FFF796E@koalephant.com>
 <CAGa2bXY6be8n86dQ-jW-BZuPCD2iWFhP+_0HGHfimEe4E517Dw@mail.gmail.com>
 <72B2986D-3C05-4929-9BDD-1A911FC9E793@koalephant.com>
Cc: Niklas Keller <me@kelunik.com>, Stanislav Malyshev <smalyshev@gmail.com>,
 "internals@lists.php.net" <internals@lists.php.net>,
 Davey Shafik <davey@php.net>, Xinchen Hui <laruence@php.net>
Message-ID: <13a6a58d-1f59-282d-45c8-8e218afc9e53@gmx.de>
Date: Thu, 20 Oct 2016 15:59:37 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <72B2986D-3C05-4929-9BDD-1A911FC9E793@koalephant.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] header() removes all header of the same name.
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 20.10.2016 at 14:15, Stephen Reay wrote:

> As with Niklas, I have no vote, so my *only* option to prevent what I consider to be a bad decision, is to post to this thread and hope that enough of those who *do* have voting rights, reject the proposal.
> 
> I understand what you’re proposing. But honestly I don’t even agree with the premise that there is a *problem* that needs to be fixed.
> 
> Did you know that if you manually set the Content-Length header to less than the actual body length, many browsers (Safari, Chrome, and FF definitely) will stop reading/processing the response at the length you specify?
> So should we also prevent setting Content-Length via header() ?
> 
> Honestly I don’t understand how this is still a discussion. The developer failed to set the $replace argument to false. At most I would expect this to result in a documentation note warning about the use of header(‘Set-Cookie…’).
> 
> I appreciate you trying to make improvements, and I’d *definitely* be in favour of the function naming cleanup you mentioned earlier, but all of this “protected” headers and extra function calls, because someone forgot to type “, false” seems ridiculous to me honestly.

Full ACK.

-- 
Christoph M. Becker