Hi,
i want some feedback, about the following idea before i write a rfc.
Problem:
The functions setcookie and setrawcookie has many parameters. Most of
them are optional and extensions (e.g. same-site) make it even more messy.
The functions setcookie and setrawcookie has 8 parameters.
bool s
LS,
Today I finished writing the RFC for implementing same site cookies in
PHP, https://wiki.php.net/rfc/same-site-cookie. I am happy to receive
your remarks on the proposal, and improve when necessary.
For those (only) interested in code, have a look at PR # 2613:
https://github.com/php/php
On 17.07.2017 at 16:12, Dan Ackroyd wrote:
> I just investigated an alleged bug related to the SQLite3 extension.
Can you please report the bug and assign it to me. I can't promise that
I'll be able to fix it, but I would take a look.
> It seems this bug occurs when PHP is compiled with the cur
Hey,
On Mon, Jul 17, 2017 at 8:58 AM, Niklas Keller wrote:
> Hi,
>>
>> > After reading related discussion on openssl-users [1], I'm not so
>> sure if
>> > we should be doing that at all...
>> >
>> > Especially I agree with this bit:
>> >
>> > "Making your code more comple
Am 17.07.2017 um 18:04 schrieb Ryan Jentzsch:
This may be a dumb question...I was under the impression that including the
config switches for the databases such as MySQL, SQLite, Postgres, etc.
that ONLY the PDO bindings are included NOT the database client itself.
Is this the case with the ex
This may be a dumb question...I was under the impression that including the
config switches for the databases such as MySQL, SQLite, Postgres, etc.
that ONLY the PDO bindings are included NOT the database client itself.
Is this the case with the exception of SQLite? In other words is the
version o
Hi Internals,
I just investigated an alleged bug related to the SQLite3 extension.
It seems this bug occurs when PHP is compiled with the current bundled
SQLite files, which are a little out of date as they are version:
"3.15.1", date: "2016-11-04".
Listed at https://sqlite.org/changes.html there
>
> Hi,
>
> > After reading related discussion on openssl-users [1], I'm not so
> sure if
> > we should be doing that at all...
> >
> > Especially I agree with this bit:
> >
> > "Making your code more complex is a far higher risk than a
> practical
> > certificate forg
