Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121253
MIME-Version: 1.0
References: <CAPyj-LD0EDYUZSOM=P9doSZRJ8LipSKKUSBHxV-bRbCV1QsYtQ@mail.gmail.com>
In-Reply-To: <CAPyj-LD0EDYUZSOM=P9doSZRJ8LipSKKUSBHxV-bRbCV1QsYtQ@mail.gmail.com>
Date: Fri, 6 Oct 2023 17:18:55 +0100
Message-ID: <CAEKnhAGd2PtSdBiw1MiGt8H2FJVe_x3nFaN5ujMGAU=2a+wheQ@mail.gmail.com>
To: Ilija Tovilo <tovilo.ilija@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000084730806070e99ac"
Subject: Re: [PHP-DEV] [RFC][Under discussion] RFC1867 for non-POST HTTP verbs
From: bukka@php.net (Jakub Zelenka)

--00000000000084730806070e99ac
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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
>
>
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.

Cheers

Jakub

Regards

Jakub

--00000000000084730806070e99ac--