Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110238
User-Agent: Cyrus-JMAP/3.3.0-dev0-487-g38013f6-fm-20200519.001-g38013f6c
Mime-Version: 1.0
Message-ID: <5c6d1ecd-aa27-4cbf-afb1-234e15e1b0bf@www.fastmail.com>
In-Reply-To: <e827814f-8a4e-4388-bc82-47c244aad978@gmail.com>
References: <e827814f-8a4e-4388-bc82-47c244aad978@gmail.com>
Date: Thu, 21 May 2020 17:06:47 -0500
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] HTTP/1.1 by default in PHP 8.0
From: larry@garfieldtech.com ("Larry Garfield")

On Thu, May 21, 2020, at 4:53 PM, Rowan Tommins wrote:
> Hi all,
>=20
> A few years ago, I posted a message suggesting that PHP improve suppor=
t=20
> for HTTP/1.1 in its stream wrapper functions:=20
> https://externals.io/message/96192
>=20
> A quick summary of the current situation:
>=20
> * HTTP/1.1 was officially standardised in January 1997, and most web=20=

> browsers had already implemented it by then
> * PHP has a very simple HTTP client implementation, used by the "http:=
"=20
> and "https:" stream wrappers, and also by extensions which make HTTP=20=

> requests, such as ext/soap
> * The client implementation defaults to advertising HTTP/1.0 requests,=
=20
> unless over-ridden by a stream context option
> * Since a lot of servers only actually talk HTTP/1.1, the client mostl=
y=20
> acts as an HTTP/1.1 client even when advertising HTTP/1.0
>=20
>=20
> In my previous message, I identified four requirements in HTTP/1.1 but=
=20
> not HTTP/1.0 that are relevant to a client:
>=20
> a) Send a "Host" header with every request. (RFC 7230 Section 5.4)
> b) Support persistent connections, or send "Connection: Close" with ea=
ch=20
> request. (RFC 7230 Section 6.1)
> c) Ignore 1xx status lines (notably, "100 Continue") "even if the clie=
nt=20
> does not expect one" (RFC 7231 Section 6.2)
> d) Support "chunked" transfer encoding (RFC 7230 Section 4.1)
>=20
>=20
> The PHP client now supports all four regardless of protocol version=20=

> configured, i.e. it always sends "Host:" and "Connection: Close"=20
> headers; and always handles "100 Continue" and "Transfer-Encoding:=20
> Chunked" if returned by the server.
>=20
> I would like to propose that the client advertises HTTP/1.1 in its=20
> requests by default in PHP 8.0.=C2=A0 Users can opt out of this behavi=
our in=20
> a fully backwards- and forwards-compatible way if necessary using a=20=

> stream context option, e.g.:=20
> https://gist.github.com/IMSoP/a685fed6589435530102d57138755511
>=20
>=20
> What are people's opinions? Does this need an RFC, or should I just=20=

> submit a PR if nobody objects?
>=20
>=20
> Regards,
>=20
> --=20
> Rowan Tommins (n=C3=A9 Collins)
> [IMSoP]

This makes complete sense to me.  Whether it needs a formal RFC or not i=
s above my pay grade, but I expect it would be just a formality if so.  =
+1

--Larry Garfield