Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96257
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.47 as permitted sender)
MIME-Version: 1.0
Sender: kalle.php@gmail.com
In-Reply-To: <5991de8e-d962-dea9-b010-d53586827db7@gmail.com>
References: <1de78ecd-74e5-438c-9744-103163218ebd@gmail.com>
 <CANUQDCheUqiYfnzW8D27MV8jK71eBUU7MsFn1Fb6A2Qv30tYLQ@mail.gmail.com> <5991de8e-d962-dea9-b010-d53586827db7@gmail.com>
Date: Wed, 5 Oct 2016 20:52:46 +0200
Message-ID: <CAJW__o2cSbwBDZHxRCFmzBkH9B0Nc7ibgi_Y6S0xojExeYJF=Q@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113986a0eaa9b9053e22aee9
Subject: Re: [PHP-DEV] Add support for HTTP/1.1
From: kalle@php.net (Kalle Sommer Nielsen)

--001a113986a0eaa9b9053e22aee9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Rowan

On Oct 5, 2016 20:21, "Rowan Collins" <rowan.collins@gmail.com> wrote:
>
> Hi all,
>
> It sounds like the feeling so far is quite positive. I'll have another
look for a dupe, then file a bug for the missing 100-continue support, and
try to work on a patch. Once that's in place, and unless anyone comes up
with other major features we need to support, we can discuss whether we
should make it the default, or at least easier to opt into.
>
>
>
> On 03/10/2016 09:43, Niklas Keller wrote ...:
>>
>> I think we already send it starting with 7.0, maybe just for 1.0,
because there are some servers that respond correctly with an HTTP/1.1
response to an HTTP/1.0 request, but fail to close the connection and imply
"Connection: close" for those requests.
>
>
> ... and on 05/10/2016 17:14, Andrea Faulds wrote:
>>
>> In order to connect to many modern websites, you need a Host: header,
and in order to use a Host: header, you need to use HTTP/1.1 (if you don't,
servers will sometimes send you back a 1.1 response anyway!).
>
>
> Indeed, checking 7.0 suggests that we are unconditionally sending both a
Host: header and Connection: Close with every request, while still claiming
"HTTP/1.0". I believe both headers are technically backwards compatible
with servers (i.e. ignored by) that genuinely speak HTTP/1.0, so this is
not technically "wrong". However, the fact that it's necessary does
strengthen the case for implementing HTTP/1.1 in full, rather than
backporting features bit by bit.
>
>
>
>
> On 04/10/2016 09:55, Bj=C3=B6rn Larsson wrote:
>>
>> Would fixing
>> this behaviour also be applicable for HTTPS?
>
>
> Yes, I'd be very surprised if this code wasn't shared between the two
contexts. (It's a little more complicated than just piping an "http"
connection through a "tls" one, because of things like SNI, but there'd be
no reason to have the actual header processing code twice.)

Afair then the code is separate in ext/standard/fopen_http_wrapper.c

>
>
> Regards,
>
> --
> Rowan Collins
> [IMSoP]
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--001a113986a0eaa9b9053e22aee9--