Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122541
Feedback-ID: ifab94697:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-205-g4dbcac4545-fm-20240301.001-g4dbcac45
Precedence: bulk
MIME-Version: 1.0
Message-ID: <6ab812e1-5fdf-4941-9d6a-c3251f20f5b9@app.fastmail.com>
In-Reply-To: 
 <CAGBsUrera8cVE5nW1H6bCSok+gOjpHCyqutaCewoXEtYju-8yA@mail.gmail.com>
References: 
 <CAGBsUrera8cVE5nW1H6bCSok+gOjpHCyqutaCewoXEtYju-8yA@mail.gmail.com>
Date: Sun, 03 Mar 2024 11:37:15 +0100
To: internals@lists.php.net
Subject: Re: [PHP-DEV] [RFC] [Discussion] Deprecate GET/POST sessions
Content-Type: multipart/alternative;
 boundary=095f78191a954e2b840aeef184c68bd4
From: rob@bottled.codes ("Rob Landers")

--095f78191a954e2b840aeef184c68bd4
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Sat, Mar 2, 2024, at 22:10, Kamil Tekiela wrote:
> Hi Internals,
>=20
> I would like to start a discussion on a new RFC
> https://wiki.php.net/rfc/deprecate-get-post-sessions
>=20
> Please let me know whether the idea is clear and the RFC is understand=
able.
>=20
> In particular, I am looking for any feedback as to why this is a bad
> idea. The primary motivation behind this RFC is to reduce potential
> security pitfalls.
>=20
> Regards,
> Kamil Tekiela
>=20

For what it is worth, I=E2=80=99ve used this with great success on Googl=
e=E2=80=99s http-based job system in their cloud. Whether that is a good=
 idea or not, I have no idea. But I suspect I=E2=80=99m not the only one=
 that has relied on this behavior.=20

=E2=80=94 Rob
--095f78191a954e2b840aeef184c68bd4
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Sat, Mar 2, =
2024, at 22:10, Kamil Tekiela wrote:<br></div><blockquote type=3D"cite" =
id=3D"qt" style=3D""><div>Hi Internals,<br></div><div><br></div><div>I w=
ould like to start a discussion on a new RFC<br></div><div><a href=3D"ht=
tps://wiki.php.net/rfc/deprecate-get-post-sessions">https://wiki.php.net=
/rfc/deprecate-get-post-sessions</a><br></div><div><br></div><div>Please=
 let me know whether the idea is clear and the RFC is understandable.<br=
></div><div><br></div><div>In particular, I am looking for any feedback =
as to why this is a bad<br></div><div>idea. The primary motivation behin=
d this RFC is to reduce potential<br></div><div>security pitfalls.<br></=
div><div><br></div><div>Regards,<br></div><div>Kamil Tekiela<br></div><d=
iv><br></div></blockquote><div><br></div><div>For what it is worth, I=E2=
=80=99ve used this with great success on Google=E2=80=99s http-based job=
 system in their cloud. Whether that is a good idea or not, I have no id=
ea. But I suspect I=E2=80=99m not the only one that has relied on this b=
ehavior.&nbsp;</div><div><br></div><div id=3D"sig121229152">=E2=80=94 Ro=
b<br></div></body></html>
--095f78191a954e2b840aeef184c68bd4--