Hi Yasuo,
I don't think we should do anything about this beyond maybe warning the
user in the manual. header() is a generic function for setting headers,
it would be surprising if it had different behaviour for cookies or
session cookies. It is possible that use of this function in this way
m
Hi all,
On Wed, Oct 19, 2016 at 1:34 PM, Yasuo Ohgaki wrote:
>
> On Wed, Oct 19, 2016 at 12:18 PM, Stephen Reay
> wrote:
>> I still have an issue with that. I believe the correct behaviour here is
>> (assuming the `replace` argument to header() is honoured) what you’re
>> seeing. Yes, it migh
Hi Stephen,
On Wed, Oct 19, 2016 at 1:34 PM, Yasuo Ohgaki wrote:
>> I realise you’re trying to remove WTF cases, but I don’t think removing
>> advanced capabilities is the way to do that.
>
> Yes. Even framework developer(?) seems to have current behavior.
To be honest, I didn't have idea what'
Hi Stephen,
On Wed, Oct 19, 2016 at 12:18 PM, Stephen Reay wrote:
> I still have an issue with that. I believe the correct behaviour here is
> (assuming the `replace` argument to header() is honoured) what you’re seeing.
> Yes, it might be *unexpected* for new users, but its also *expected* by
Hi Yasuo,
I still have an issue with that. I believe the correct behaviour here is
(assuming the `replace` argument to header() is honoured) what you’re seeing.
Yes, it might be *unexpected* for new users, but its also *expected* by
millions of current users/projects.
I would suggest perhaps a
Hi all,
On Tue, Oct 18, 2016 at 4:31 PM, Yasuo Ohgaki wrote:
> I understand why header() is made to remove all headers of the same
> name. This is needed in some cases, but it does not work well for some
> cases.
>
> We need to decide what to do with
> https://bugs.php.net/bug.php?id=72997
>
> Th
