Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96524 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70591 invoked from network); 20 Oct 2016 12:42:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Oct 2016 12:42:20 -0000 Authentication-Results: pb1.pair.com header.from=php-lists@koalephant.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=php-lists@koalephant.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain koalephant.com designates 206.123.115.54 as permitted sender) X-PHP-List-Original-Sender: php-lists@koalephant.com X-Host-Fingerprint: 206.123.115.54 mail1.25mail.st Received: from [206.123.115.54] ([206.123.115.54:54989] helo=mail1.25mail.st) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D9/D8-24564-BABB8085 for ; Thu, 20 Oct 2016 08:42:20 -0400 Received: from [10.0.1.23] (unknown [183.89.46.225]) by mail1.25mail.st (Postfix) with ESMTPSA id 7A5BE60ABB; Thu, 20 Oct 2016 12:41:53 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) In-Reply-To: Date: Thu, 20 Oct 2016 19:41:47 +0700 Cc: Niklas Keller , Stanislav Malyshev , "internals@lists.php.net" , Davey Shafik , Xinchen Hui Content-Transfer-Encoding: quoted-printable Message-ID: <5411747E-8AD8-441D-AFBA-0B80A7F550A1@koalephant.com> References: <1eab7492-596c-ffd2-81ed-0eb9256a033e@gmail.com> <0B722A15-A29F-498B-987F-F6BA5AA49EEF@bobs-bits.com> <59D6B40B-DC64-43A3-AED4-CD5C9C15B6BA@koalephant.com> <72B2986D-3C05-4929-9BDD-1A911FC9E793@koalephant.com> To: Yasuo Ohgaki X-Mailer: Apple Mail (2.3124) Subject: Re: [PHP-DEV] header() removes all header of the same name. From: php-lists@koalephant.com (Stephen Reay) Hi Yasuo, > On 20 Oct 2016, at 19:21, Yasuo Ohgaki wrote: >=20 > Hi Ptephen, >=20 > On Thu, Oct 20, 2016 at 9:15 PM, 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. >=20 > It's okay, but aren't I and framework developers on the same side? Apparently not. I expect people using my work to read the documentation. = I don=E2=80=99t remove mysql support because they don=E2=80=99t = understand why a =E2=80=9CDELETE * FROM foo=E2=80=9D query deleted all = their data. Similarly I don=E2=80=99t see why it=E2=80=99s a bug to = remove headers when you leave $replace to the default of true. >=20 > I don't want to get bug report that session lost or some important > cookie lost somehow. Why is your concern so focussed on solving problems for inexperienced = developers, who are effectively using functions incorrectly, at the = expense of experienced developers who are doing the right thing? This response effectively encourages bad behaviour (did the reporter = even check the docs for header() to see why it=E2=80=99s replacing the = session cookie? How many bug reports do you think you=E2=80=99re going to get saying = =E2=80=9Cheader() no longer supports set-cookie headers=E2=80=9D.=20 >=20 > Framework developers don't want to get bug report that user logouts or > some important cookie lost somehow. >=20 > It's better that we have header*() and cookie*() function for > dedicated purpose, isn't it? Having dedicated functions for setting cookies, yes that makes sense. Removing that functionality from header() makes no sense. A cookie is = still a header. >=20 > Regards, >=20 > -- > Yasuo Ohgaki > yohgaki@ohgaki.net >=20