Re: [hybi] workability (or otherwise) of HTTP upgrade

Mark Nottingham <mnot@mnot.net> Tue, 07 December 2010 06:12 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8455A3A691D for <hybi@core3.amsl.com>; Mon, 6 Dec 2010 22:12:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.655
X-Spam-Level:
X-Spam-Status: No, score=-104.655 tagged_above=-999 required=5 tests=[AWL=-2.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WbXNVfTewzH3 for <hybi@core3.amsl.com>; Mon, 6 Dec 2010 22:12:49 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 750633A6914 for <hybi@ietf.org>; Mon, 6 Dec 2010 22:12:49 -0800 (PST)
Received: from chancetrain-lm.mnot.net (unknown [118.209.2.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D27B022E1EB; Tue, 7 Dec 2010 01:14:06 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20101207061028.GM19364@1wt.eu>
Date: Tue, 07 Dec 2010 17:14:02 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E45BB7E0-D503-4294-9429-4E8880FC1F6C@mnot.net>
References: <AANLkTin6=8_Bhn2YseoSHGh1OSkQzsYrTW=fMiPvYps1@mail.gmail.com> <20101126000352.ad396b9a.eric@bisonsystems.net> <AANLkTimzQyG4hugOvHqoNrBrZFA4fGbGXQ7MZ2i+68dO@mail.gmail.com> <BB947F6D-15AA-455D-B830-5E12C80C1ACD@mnot.net> <81870DB1-B177-4253-8233-52C4168BE99D@apple.com> <F4D1B715-3606-4E9A-BFB2-8B7BC11BE331@mnot.net> <20101207061028.GM19364@1wt.eu>
To: Willy Tarreau <w@1wt.eu>
X-Mailer: Apple Mail (2.1082)
Cc: hybi HTTP <hybi@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: [hybi] workability (or otherwise) of HTTP upgrade
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Dec 2010 06:12:50 -0000

On 07/12/2010, at 5:10 PM, Willy Tarreau wrote:

> In my opinion the problem is not here, but the adoption rate depending
> on the port. Many organisations implement URL filtering on port 80,
> white-list based filtering on 443 and nothing else around. If you want
> to deploy a site which quickly gets a lot of traffic, port 80 clearly
> is the most suited, which is even more true considering that long polling
> mechanisms already work over that port.

Quantify 'many.' According to Adam's paper, ~13% of clients will fail to negotiate with a CONNECT-based solution. Is "many" > 13% of the Internet?


> Also, being able to switch from HTTP to WS over a same socket for some
> services can save one round trip, but that's marginal in most situations,
> except from mobile phones.


Would they negotiate back to HTTP if they need to fetch an image? 



--
Mark Nottingham   http://www.mnot.net/