Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111202
To: PHP Internals <internals@lists.php.net>
References: <e827814f-8a4e-4388-bc82-47c244aad978@gmail.com>
Message-ID: <9d28ade6-1a70-9850-3bc0-64050c0dcbe4@gmail.com>
Date: Mon, 27 Jul 2020 23:24:48 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <e827814f-8a4e-4388-bc82-47c244aad978@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: HTTP/1.1 by default in PHP 8.0
From: rowan.collins@gmail.com (Rowan Tommins)

Hi all,

A couple of months ago I revived my suggestion to make stream wrappers 
advertise HTTP/1.1 by default (full message below), and then Real Life 
intervened and I didn't raise the PR.

The implementation (which is a one-character change) is now here: 
https://github.com/php/php-src/pull/5899

I realise it's now rather last-minute for 8.0, so if anyone thinks it 
should have more careful thought, or an RFC, it will have to wait. If 
there are no objections, though, it would be nice to have it merged 
before the freeze.

Thanks,
Rowan



On 21/05/2020 22:53, Rowan Tommins wrote:
> Hi all,
>
> A few years ago, I posted a message suggesting that PHP improve 
> support for HTTP/1.1 in its stream wrapper functions: 
> https://externals.io/message/96192
>
> A quick summary of the current situation:
>
> * HTTP/1.1 was officially standardised in January 1997, and most web 
> browsers had already implemented it by then
> * PHP has a very simple HTTP client implementation, used by the 
> "http:" and "https:" stream wrappers, and also by extensions which 
> make HTTP requests, such as ext/soap
> * The client implementation defaults to advertising HTTP/1.0 requests, 
> unless over-ridden by a stream context option
> * Since a lot of servers only actually talk HTTP/1.1, the client 
> mostly acts as an HTTP/1.1 client even when advertising HTTP/1.0
>
>
> In my previous message, I identified four requirements in HTTP/1.1 but 
> not HTTP/1.0 that are relevant to a client:
>
> a) Send a "Host" header with every request. (RFC 7230 Section 5.4)
> b) Support persistent connections, or send "Connection: Close" with 
> each request. (RFC 7230 Section 6.1)
> c) Ignore 1xx status lines (notably, "100 Continue") "even if the 
> client does not expect one" (RFC 7231 Section 6.2)
> d) Support "chunked" transfer encoding (RFC 7230 Section 4.1)
>
>
> The PHP client now supports all four regardless of protocol version 
> configured, i.e. it always sends "Host:" and "Connection: Close" 
> headers; and always handles "100 Continue" and "Transfer-Encoding: 
> Chunked" if returned by the server.
>
> I would like to propose that the client advertises HTTP/1.1 in its 
> requests by default in PHP 8.0.  Users can opt out of this behaviour 
> in a fully backwards- and forwards-compatible way if necessary using a 
> stream context option, e.g.: 
> https://gist.github.com/IMSoP/a685fed6589435530102d57138755511
>
>
> What are people's opinions? Does this need an RFC, or should I just 
> submit a PR if nobody objects?
>
>
> Regards,
>

-- 
Rowan Tommins (né Collins)
[IMSoP]