Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:108524
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
In-Reply-To: <3efc8ed3-61a8-dad8-dd1f-207217589eba@allenjb.me.uk>
Date: Wed, 12 Feb 2020 16:46:22 -0600
Cc: PHP Internals List <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <ADC3F146-EB49-463D-8FB7-323C35E98C71@pmjones.io>
References: <50BD013E-CF72-414C-BBC0-A7A2E45CBDDB@pmjones.io>
 <3efc8ed3-61a8-dad8-dd1f-207217589eba@allenjb.me.uk>
To: AllenJB <php.lists@allenjb.me.uk>,
 "Kingsquare.nl - Robin Speekenbrink" <robin@kingsquare.nl>
Subject: Re: [PHP-DEV] RFC: Server-Side Request and Response Objects (v2)
From: pmjones@pmjones.io ("Paul M. Jones")

Hi Allen & Robin,

Allen, you asked:

> On Feb 12, 2020, at 15:27, AllenJB <php.lists@allenjb.me.uk> wrote:
>=20
> This might be more a "future scope" thing, but I would like to see a =
way to access the raw request body as part of this. Currently (as far as =
I know) the only way is to open/read php://input, which isn't =
particularly intuitive in my opinion.


Robin asked the same thing earlier:

> On Feb 11, 2020, at 08:24, Kingsquare.nl - Robin Speekenbrink =
<robin@kingsquare.nl> wrote:
>=20
> What i haven't clearly seen in the RFC nor the interfaces of the =
proposed objects: how will this handle PUT / php:://input / raw posted =
data? Or am i missing something?

Answer: the php://input stream is accessible via the ServerRequest =
$content property; see =
<https://github.com/pmjones/ext-request#content-related>.


--=20
Paul M. Jones
pmjones@pmjones.io
http://paul-m-jones.com

Modernizing Legacy Applications in PHP
https://leanpub.com/mlaphp

Solving the N+1 Problem in PHP
https://leanpub.com/sn1php