Re: [RFC][Under discussion] RFC1867 for non-POST HTTP verbs
| From: | Marco Aurélio Deleu | Date: | Fri, 06 Oct 2023 22:55:31 +0000 |
| Subject: | Re: [RFC][Under discussion] RFC1867 for non-POST HTTP verbs | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-121259@lists.php.net to get a copy of this message | ||
Marco Deleu
> On 6 Oct 2023, at 19:39, Ben Ramsey <ramsey@php.net> wrote:
>
> On 10/6/23 11:18, Jakub Zelenka wrote:
>> Hi,
>>> On Fri, Oct 6, 2023 at 2:44 PM Ilija Tovilo <tovilo.ilija@gmail.com> wrote:
>>> https://wiki.php.net/rfc/rfc1867-non-post
>>>
>>>
>> 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 placed
>> in the current PR) as it has nothing to do with html IMHO.
>
>
> Maybe it should go in main/rfc1867.c? That's where the php_rfc1867_callback lives, and
> this seems somewhat related to that.
>
> Cheers,
> Ben
>
Just wanted to mention that maybe this is a great opportunity to create a request_ family and start
with request_parse_post_data