Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121263
MIME-Version: 1.0
References: <CAPyj-LD0EDYUZSOM=P9doSZRJ8LipSKKUSBHxV-bRbCV1QsYtQ@mail.gmail.com>
In-Reply-To: <CAPyj-LD0EDYUZSOM=P9doSZRJ8LipSKKUSBHxV-bRbCV1QsYtQ@mail.gmail.com>
Date: Sat, 7 Oct 2023 14:55:49 +0200
Message-ID: <CAPyj-LCMXLQ34tuSMJJ+0c63s691FksZf6RknjwtUdK-d3Zx9Q@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 Marco

Please note that you have accidentally created a new thread. I'm
responding from the main thread.

> >>> On Fri, Oct 6, 2023 at 2:44=E2=80=AFPM Ilija Tovilo <tovilo.ilija@gma=
il.com> wrote:
> >>> https://wiki.php.net/rfc/rfc1867-non-post
>
> Just wanted to mention that maybe this is a great opportunity to create a=
 request_ family and start with request_parse_post_data

Something like request_parse_body() could work. That should satisfy
both your and Micha=C5=82s request. This naming extends nicely to other
formats if added later on.

This reminded me that it should be specified what happens when the
format is not supported (i.e. anything but multipart or urlencoded
formats). The automatically invoked behavior does nothing and leaves
the input stream unconsumed so that the PHP script can process it. For
the explicitly invoked version we should throw an exception to inform
the user that nothing happened.

Ilija