Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121259
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Fri, 6 Oct 2023 19:55:31 -0300
Message-ID: <4AD2C29F-FD37-49D0-AA61-B91740231067@gmail.com>
References: <65208c89.250a0220.3ebd5.0948SMTPIN_ADDED_MISSING@mx.google.com>
Cc: internals@lists.php.net
In-Reply-To: <65208c89.250a0220.3ebd5.0948SMTPIN_ADDED_MISSING@mx.google.com>
To: Ben Ramsey <ramsey@php.net>
Subject: Re: [PHP-DEV] [RFC][Under discussion] RFC1867 for non-POST HTTP verbs
From: deleugyn@gmail.com (=?utf-8?Q?Marco_Aur=C3=A9lio_Deleu?=)



Marco Deleu=20

> On 6 Oct 2023, at 19:39, Ben Ramsey <ramsey@php.net> wrote:
>=20
> =EF=BB=BFOn 10/6/23 11:18, Jakub Zelenka wrote:
>> Hi,
>>> On Fri, Oct 6, 2023 at 2:44=E2=80=AFPM Ilija Tovilo <tovilo.ilija@gmail.=
com> wrote:
>>> https://wiki.php.net/rfc/rfc1867-non-post
>>>=20
>>>=20
>> It should probably explicitly mention that it uses the same inis like
>> max_input_vars, max_file_uploads and max_multipart_body_parts.
>> It's kind of strange function as I can't decide where it should be placed=
.
>> I think it might be better as a stream function if it accepts only stream=
.
>> It means it could go to stream funcs and be called stream_parse_post_data=

>> instead but not sure about. But not 100% sure about it as it doesn't
>> exactly fit there. But seems better than html functions (where it's place=
d
>> in the current PR) as it has nothing to do with html IMHO.
>=20
>=20
> Maybe it should go in main/rfc1867.c? That's where the php_rfc1867_callbac=
k lives, and this seems somewhat related to that.
>=20
> Cheers,
> Ben
>=20

Just wanted to mention that maybe this is a great opportunity to create a re=
quest_ family and start with request_parse_post_data=