On Tue, Oct 18, 2016 at 5:54 PM, Stephen Reay <step...@bobs-bits.com> wrote:
> If the replace flag was fixed, isn’t this then just a case of making sure
> userland sets replace to false if they want existing set-cookie headers
Yes and no.
If users use the replace flag correctly, then it will work. However, I
don't expect users set replace flag correctly. If replace flag's
default was opposite, it would work better.
> Removing the ability to write a custom Set-Cookie header introduces a bigger
> problem than the current one, IMO.
OK. Let's just fix the replace flag and document removing 'Set-Cookie'
header by header() may result in unwanted results.
Everyone is ok with this?
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php