Re: Invalid HTTP2 preface handling?
Michael Sweet <msweet@apple.com> Wed, 11 February 2015 03:18 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ietf.org@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25E011A1B7F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 10 Feb 2015 19:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.802
X-Spam-Level:
X-Spam-Status: No, score=-6.802 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SvaifgfJ6qM for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 10 Feb 2015 19:18:11 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A3B31A0362 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 10 Feb 2015 19:18:11 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YLNlP-0003cF-5V for ietf-http-wg-dist@listhub.w3.org; Wed, 11 Feb 2015 03:14:55 +0000
Resent-Date: Wed, 11 Feb 2015 03:14:55 +0000
Resent-Message-Id: <E1YLNlP-0003cF-5V@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <msweet@apple.com>) id 1YLNlJ-0003bY-Nm for ietf-http-wg@listhub.w3.org; Wed, 11 Feb 2015 03:14:49 +0000
Received: from mail-out2.apple.com ([17.151.62.25] helo=mail-in2.apple.com) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <msweet@apple.com>) id 1YLNlI-0007SI-7Z for ietf-http-wg@w3.org; Wed, 11 Feb 2015 03:14:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1423624460; x=2287538060; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=3Bpz//SJbsztCMdDYFWjtc9TYcJywEJrIPy3cCFgGvQ=; b=cf4+nwtO9ls6QgOnBeihNrqWBNyIpfq6nCvwITi5iO5+XbJUmpUjuFFZTw26ER5M mn2sAh0kulNQVMdhAZzrpn4X/HZ8HuWIxMUbBYyB8LoJhjY52sTD6y1dA8NGOFMl 00d2lwdbz2pzQ0S6Tt0XlfHQrE0AlfY1OZ5/iADFDV3nJdALwHpP17PGiJNutTqN bmcVmdpvCH5Wvn5PfjVgSJixxY2aC5VcefqJ7Ne9Df4LE44wTbFOk0m/CcsbfktL RxZcGcGdnwZqWqVU6ZPyMkUq3Yt2Cuw1xLlUSg/FAfn41DGiK6+gg5H0wZIz4sNh WF5HlmhosZn4SDijJ8661Q==;
Received: from relay6.apple.com (relay6.apple.com [17.128.113.90]) by mail-in2.apple.com (Apple Secure Mail Relay) with SMTP id DB.35.00537.C09CAD45; Tue, 10 Feb 2015 19:14:20 -0800 (PST)
X-AuditID: 11973e11-f79e16d000000219-bf-54dac90c2070
Received: from sesame.apple.com (sesame.apple.com [17.128.115.128]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by relay6.apple.com (Apple SCV relay) with SMTP id CE.03.05157.9D8CAD45; Tue, 10 Feb 2015 19:13:29 -0800 (PST)
Received: from [17.153.53.122] (unknown [17.153.53.122]) by sesame.apple.com (Oracle Communications Messaging Server 7.0.5.30.0 64bit (built Oct 22 2013)) with ESMTPSA id <0NJL006Z77NUOS50@sesame.apple.com> for ietf-http-wg@w3.org; Tue, 10 Feb 2015 19:14:20 -0800 (PST)
MIME-version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-type: text/plain; charset="us-ascii"
From: Michael Sweet <msweet@apple.com>
In-reply-to: <54DABF12.70609@treenet.co.nz>
Date: Tue, 10 Feb 2015 22:14:18 -0500
Cc: ietf-http-wg@w3.org
Content-transfer-encoding: quoted-printable
Message-id: <1467A259-E3B4-4249-BAC4-CC4D1BA1935D@apple.com>
References: <CAH_y2NE5Sa625XEec5WXJ7LdjK+h1b4M=Fc-_iGj2ZQKa1q_jg@mail.gmail.com> <5C91DE2C-BC82-4142-B292-815EED3627EC@mnot.net> <54DAA3A4.8060608@treenet.co.nz> <CAH_y2NG0_Y9nnDjLd2Fc_5wBessfy0DOfKBfkH8NiKjyzAiRVg@mail.gmail.com> <54DABF12.70609@treenet.co.nz>
To: Amos Jeffries <squid3@treenet.co.nz>
X-Mailer: Apple Mail (2.2070.6)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrHLMWRmVeSWpSXmKPExsUi2FAYpctz8laIwYtpBhaHW2YxOTB6HJ23 nzWAMYrLJiU1J7MstUjfLoEr423rFOaCpxwVk/rfMDUw/mHrYuTgkBAwkVh4VriLkRPIFJO4 cG89G4gtJLCXUeLIdlWIuInEp7UvmboYuYDifUwS1ya+Y4RwJjNJzF3/hBGkSlhAR2LuqU1g 3bwCBhJfdh5lB7GZBbQk1u88zgRiswmoSfye1McKsphTQFvi1hk5kDCLgKrElu2/mSDKxSW6 O3exQtjaEk/eXWCFGGkjcfzXQagj+pkknjSCzOfgEBHQkLh0oBLiF3mJnk3pEDd/ZJWYvF9x AqPwLCQHzUJy0CwkGxYwMq9iFMpNzMzRzcwz0kssKMhJ1UvOz93ECArg6XaCOxiPr7I6xCjA wajEw/th060QIdbEsuLK3EOM0hwsSuK8ed43QoQE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUw HjDK3G7DtMwhqMHT6phhwHwJOd/7t/prLj7LnyWvZDkv88gewa2HlOPXtrRXxKV9si9ZZR/1 8kTy/XO8xSrnZ0wo4TjC2ziJ4fqsX4tmya+ofPG4Q2c37+02Kdn3vZntX2OX9vCtblcWV4hI j/i38oxW3gTN9yFqjYsT53bJTAua+GHVJfkEJZbijERDLeai4kQAU1dDEEECAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUi2FDcoHvzxK0Qg95lphaHW2YxOTB6HJ23 nzWAMYrLJiU1J7MstUjfLoEr423rFOaCpxwVk/rfMDUw/mHrYuTkkBAwkfi09iUThC0mceHe eqA4F4eQQB+TxLWJ7xghnMlMEnPXP2EEqRIW0JGYe2oTWDevgIHEl51H2UFsZgEtifU7j4NN YhNQk/g9qY+1i5GDg1NAW+LWGTmQMIuAqsSW7b+ZIMrFJbo7d7FC2NoST95dYIUYaSNx/NdB Joi9/UwSTxpB5nNwiAhoSFw6UAliSgjIS/RsSp/AKDALyRGzkBwxC8nUBYzMqxgFilJzEivN 9BILCnJS9ZLzczcxgsOuMGoHY8Nyq0OMAhyMSjy8HzbdChFiTSwrrsw9xCjBwawkwiu8GSjE m5JYWZValB9fVJqTWnyIUZqDRUmcd8GXiyFCAumJJanZqakFqUUwWSYOTqkGRr8C/+DIiclZ ul72i8KOXjToF926x+1eNveyPo0ffcxR69/9tYg9pfIw95Rw+VMn+5nLn/+JNV/rPoGDVbP4 Sd9/r4vmn2Y+tTqpPin0+qGPE+087rVvsJN6w9V6eurO8E9T9ZMU0twfsjfc+n/l1CX7C/nG hxo/PZHYUXbuotm9XTu234zTq1ZiKc5INNRiLipOBACSZyCxNwIAAA==
Received-SPF: pass client-ip=17.151.62.25; envelope-from=msweet@apple.com; helo=mail-in2.apple.com
X-W3C-Hub-Spam-Status: No, score=-5.1
X-W3C-Hub-Spam-Report: AWL=-1.046, BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001
X-W3C-Scan-Sig: maggie.w3.org 1YLNlI-0007SI-7Z 85bf49b16508cc205e2e52d00dea1558
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Invalid HTTP2 preface handling?
Archived-At: <http://www.w3.org/mid/1467A259-E3B4-4249-BAC4-CC4D1BA1935D@apple.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/28810
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Um, with all due respect HTTP/1.1 is a Proposed Standard with a lot of years of deployment, while HTTP/2.0 is *almost* a Draft Standard. Why are we talking about "a deprecated 1.x"? > On Feb 10, 2015, at 9:31 PM, Amos Jeffries <squid3@treenet.co.nz> wrote: > > On 11/02/2015 2:27 p.m., Greg Wilkins wrote: >> Amos, >> >> that is a good way of doing it - more or less like an upgrade, but without >> the complexity of having to inject the settings frame and HTTP/1 request >> into the server. While I hear what Mark says about caution, I really >> don't see a great risk here and thus will look at supporting it also. > > I agree with Mark completely about the 2.0 -> 1.1 transition being > dangerous. 1.1 has a scary amount of legacy tolerances and gaps where > nastiness can squeeze through. > > Beyond safety is the other issue of promoting 2.0 at every opportunity > while remaining compatible with a deprecated 1.x. > > Amos > > _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair
- Invalid HTTP2 preface handling? Greg Wilkins
- Re: Invalid HTTP2 preface handling? Mark Nottingham
- Re: Invalid HTTP2 preface handling? Amos Jeffries
- Re: Invalid HTTP2 preface handling? Greg Wilkins
- Re: Invalid HTTP2 preface handling? Amos Jeffries
- Re: Invalid HTTP2 preface handling? Michael Sweet
- Re: Invalid HTTP2 preface handling? Greg Wilkins
- Re: Invalid HTTP2 preface handling? Martin Thomson
- Re: Invalid HTTP2 preface handling? Willy Tarreau
- Re: Invalid HTTP2 preface handling? Julian Reschke
- Re: Invalid HTTP2 preface handling? Poul-Henning Kamp
- Re: Invalid HTTP2 preface handling? Mark Nottingham
- Re: Invalid HTTP2 preface handling? Greg Wilkins