Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121934
MIME-Version: 1.0
References: <CAPyj-LD0EDYUZSOM=P9doSZRJ8LipSKKUSBHxV-bRbCV1QsYtQ@mail.gmail.com>
In-Reply-To: <CAPyj-LD0EDYUZSOM=P9doSZRJ8LipSKKUSBHxV-bRbCV1QsYtQ@mail.gmail.com>
Date: Tue, 5 Dec 2023 21:29:18 +0100
Message-ID: <CAPyj-LBTbfwrkoiMASFhTnG1DC-7QFt4QKh0OzA1_knEiv=KRQ@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [RFC][Under discussion] RFC1867 for non-POST HTTP verbs
From: tovilo.ilija@gmail.com (Ilija Tovilo)

Hi everyone

On Fri, Oct 6, 2023 at 3:44=E2=80=AFPM Ilija Tovilo <tovilo.ilija@gmail.com=
> wrote:
>
> I'd like to announce an RFC that proposes adding a new function called
> parse_post_data() to expose the existing functionality to userland, so
> that the mechanism can be used for other HTTP verbs.
>
> https://wiki.php.net/rfc/rfc1867-non-post

I took a closer look at RoadRunner regarding file uploads and noticed
that $input_stream will not be useful to it after all. RoadRunner
handles files directly in its Go server by parsing the multipart body,
storing any files to disk, and only transferring the file handles
(along with any post data) to the PHP workers. New SAPIs could instead
tweak sapi_module.read_post() when handling a new request. We can add
these parameters if somebody can present a valid use-case, for now I
opted to remove the $input_stream and $content_type parameters.

Please let me know if you have any more feedback. I will wait at least
2 weeks before going forward with a vote, as this is a bigger change
to the RFC.

Ilija