Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96257 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81828 invoked from network); 5 Oct 2016 18:52:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Oct 2016 18:52:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=kalle.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kalle.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.47 as permitted sender) X-PHP-List-Original-Sender: kalle.php@gmail.com X-Host-Fingerprint: 209.85.214.47 mail-it0-f47.google.com Received: from [209.85.214.47] ([209.85.214.47:36118] helo=mail-it0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7B/57-23443-30C45F75 for ; Wed, 05 Oct 2016 14:52:52 -0400 Received: by mail-it0-f47.google.com with SMTP id 188so116566632iti.1 for ; Wed, 05 Oct 2016 11:52:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AEnd6xPTi5Y6XhrINGCaynWKka4bwl8R28ubL8esGGQ=; b=SDrA7nw7A4tR1JcCQ0Atl/O11bxejoCzN/AAcfUcYap28Mj/rDQKHULjFmy62Ls/wA iyQrGY8CXNi1Ep7e+GrP+1PDQxc1qyBLrle5ryoxmd9Wb/slejLGBCCSJSRyHWrxda1B WPhpV07xLxY0ohGee1KmeoUBxkAvjcYwzjeG/a37w6IIOrVm048Of309Db00mfSGCS/u PqHY0F8i/vs0UHcGlL2oin/f4pqTtTV6ptFGmAe8PnilxpQYVqjGCGwZW7cPF+aRvRxQ xMQm+1X18QTgoyAwTVZdD50bw/is8oD64NoB8NdcI/GX3iAucrDlVPhs99BudDvrLtQg u5Tg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=AEnd6xPTi5Y6XhrINGCaynWKka4bwl8R28ubL8esGGQ=; b=Ljf7CfpCRzQYn0hZe8Mt2qHQWQR46LpfDIHaSolnei8ncJTOizX0Wa0ntsoVg62Niq BLn/vboyj3hBHkyeYIj1Ulv/HSGOit86F0JYWWKf+4SXVGlojKq4qRnFMShZG1Ehhtvx F3dmHyj5dTZsn58sS+96DRMC2ufwm/bK7AC7bxAxvnf98Qe3XNzAmSvRWKwE+pCXDCmE gbfgeXYUsc5+u90pQkC6mmt92930/1urGm8GI7zL2IuC67N1mkV5nNjx29nsSAD0vslD gfY/nh/uCM2JxUCT+IBJfM0UIdeXguxchKb3ZxUnaA0QNbK40jGay3Yq/Cgetm6Yextb IPQw== X-Gm-Message-State: AA6/9RmNMOXNE/az2+f/SyLXP7gnyC8bYOfsRzfM6pPlZysMkwEOoO94apyACykHLoP5R4EzByKz5Jd7QyZB1Q== X-Received: by 10.107.44.3 with SMTP id s3mr11212818ios.236.1475693567972; Wed, 05 Oct 2016 11:52:47 -0700 (PDT) MIME-Version: 1.0 Sender: kalle.php@gmail.com Received: by 10.107.19.233 with HTTP; Wed, 5 Oct 2016 11:52:46 -0700 (PDT) Received: by 10.107.19.233 with HTTP; Wed, 5 Oct 2016 11:52:46 -0700 (PDT) In-Reply-To: <5991de8e-d962-dea9-b010-d53586827db7@gmail.com> References: <1de78ecd-74e5-438c-9744-103163218ebd@gmail.com> <5991de8e-d962-dea9-b010-d53586827db7@gmail.com> Date: Wed, 5 Oct 2016 20:52:46 +0200 X-Google-Sender-Auth: 8H1gLyDF7Gd66tMQ2CsQbXhZpdw Message-ID: To: Rowan Collins Cc: Internals 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" 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--