Re: RFC1867 (multipart/form-data) PUT requests
| From: | Ilija Tovilo | Date: | Tue, 27 Jun 2023 09:01:12 +0000 |
| Subject: | Re: RFC1867 (multipart/form-data) PUT requests | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-120693@lists.php.net to get a copy of this message | ||
Hi Ben, Hi Rowan
On Mon, Jun 26, 2023 at 8:55 PM Ben Ramsey <ben@benramsey.com> wrote:
>
> > On Jun 20, 2023, at 06:06, Rowan Tommins <rowan.collins@gmail.com> wrote:
> >
> > On Tue, 20 Jun 2023 at 10:25, Ilija Tovilo <tovilo.ilija@gmail.com> wrote:
> >
> >> Introduce a new function (currently named populate_post_data()) to
> >> read the input stream and populate the $_POST and $_FILES
> >> superglobals.
> >
> > How about "request_form_populate_globals"?
The word "form" seems a bit out of place (even though it appears in
both multipart/form-data and application/x-www-form-urlencoded),
because this function is mainly targeted at PUT/PATCH requests for
REST APIs. Maybe request_body_populate_globals?
> Another option for the name:
populate_multipart_form_data().
I avoided the term "multipart" because the function technically also
works for application/x-www-form-urlencoded requests. It's less
necessary for the reasons outlined in my previous email, but it would
allow for consistent handling of such requests for all HTTP methods.
Some people on GitHub voiced that they would prefer an INI setting.
Therefore I will create an RFC accordingly.
Ilija