Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111214
MIME-Version: 1.0
References: <e827814f-8a4e-4388-bc82-47c244aad978@gmail.com>
 <9d28ade6-1a70-9850-3bc0-64050c0dcbe4@gmail.com> <CAESVnVrajMYWoV9ce6xndsXKszTseP2UJcK_6VN0e_hGDa6SYg@mail.gmail.com>
 <CALKiJKq3X+jV3r9dMFOu_FynpZCjj7j2Bqk7SvAH4mb7uQdfZg@mail.gmail.com> <3a2e620a-48ab-278c-4ef7-e5948f1404b4@ofcourseimright.com>
In-Reply-To: <3a2e620a-48ab-278c-4ef7-e5948f1404b4@ofcourseimright.com>
Date: Tue, 28 Jul 2020 10:23:40 +0100
Message-ID: <CALKiJKrrOrjtRntr=_uUg+viHN74y0EXn7qFjeLQifYAxSkkCQ@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000556d0605ab7cfffc"
Subject: Re: [PHP-DEV] Re: HTTP/1.1 by default in PHP 8.0
From: rowan.collins@gmail.com (Rowan Tommins)

--000000000000556d0605ab7cfffc
Content-Type: text/plain; charset="UTF-8"

On Tue, 28 Jul 2020 at 10:13, Eliot Lear <lear@ofcourseimright.com> wrote:

> I think this is ok for a client.  I'd feel differently about servers.
> There may be other subtle changes between 1.0 and 1.1.  Have you
> reviewed those?
>


I did my best; see previous mails in this thread for my analysis. It's
surprisingly hard to find a succinct summary of what _requirements_ are
changed between specs, rather than just new features.

As I say, though, that will only affect us if a server is strictly
implementing both versions of the spec and behaving differently because we
send HTTP/1.0. The fact that various HTTP 1.1 features are enabled in our
client code by default suggests that is frequently not the case.

Regards,
-- 
Rowan Tommins
[IMSoP]

--000000000000556d0605ab7cfffc--