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

Adam Barth <ietf@adambarth.com> Wed, 01 December 2010 18:00 UTC

Return-Path: <ietf@adambarth.com>
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 06D6A3A6C6B for <hybi@core3.amsl.com>; Wed, 1 Dec 2010 10:00:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.768
X-Spam-Level:
X-Spam-Status: No, score=-3.768 tagged_above=-999 required=5 tests=[AWL=-0.791, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 WgT0wpxSqdmz for <hybi@core3.amsl.com>; Wed, 1 Dec 2010 10:00:31 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 238FB3A6C6D for <hybi@ietf.org>; Wed, 1 Dec 2010 10:00:31 -0800 (PST)
Received: by yxp4 with SMTP id 4so704168yxp.31 for <hybi@ietf.org>; Wed, 01 Dec 2010 10:01:44 -0800 (PST)
Received: by 10.100.106.8 with SMTP id e8mr6529132anc.99.1291226504502; Wed, 01 Dec 2010 10:01:44 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id c7sm222991ana.37.2010.12.01.10.01.42 (version=SSLv3 cipher=RC4-MD5); Wed, 01 Dec 2010 10:01:43 -0800 (PST)
Received: by iwn40 with SMTP id 40so9092878iwn.31 for <hybi@ietf.org>; Wed, 01 Dec 2010 10:01:41 -0800 (PST)
Received: by 10.231.11.3 with SMTP id r3mr6333408ibr.53.1291226501720; Wed, 01 Dec 2010 10:01:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.12.77 with HTTP; Wed, 1 Dec 2010 10:01:09 -0800 (PST)
In-Reply-To: <F96E5CE9-CA7D-4B70-8260-F05456D021FB@gbiv.com>
References: <AANLkTin6=8_Bhn2YseoSHGh1OSkQzsYrTW=fMiPvYps1@mail.gmail.com> <20101126000352.ad396b9a.eric@bisonsystems.net> <AANLkTimzQyG4hugOvHqoNrBrZFA4fGbGXQ7MZ2i+68dO@mail.gmail.com> <4CF615B2.9010304@rowe-clan.net> <F96E5CE9-CA7D-4B70-8260-F05456D021FB@gbiv.com>
From: Adam Barth <ietf@adambarth.com>
Date: Wed, 01 Dec 2010 10:01:09 -0800
Message-ID: <AANLkTimi5HL56PD9gLHUWs=mcbV3Eaz=GOsK38sxPevb@mail.gmail.com>
To: "Roy T. Fielding" <fielding@gbiv.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: "William A. Rowe Jr." <wrowe@rowe-clan.net>, 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: Wed, 01 Dec 2010 18:00:32 -0000

On Wed, Dec 1, 2010 at 9:45 AM, Roy T. Fielding <fielding@gbiv.com> wrote:
> On Dec 1, 2010, at 1:30 AM, William A. Rowe Jr. wrote:
>> On 11/26/2010 6:55 AM, Greg Wilkins wrote:
>>>
>>> And do you get similar feeling to think about using the CONNECT method
>>> to establish tunnels for arbitrary protocols?
>>
>> CONNECT suffers from the same issues you identify is deploying a new port.
>> Namely, http servers will reject those requests.  Leveraging CONNECT
>> successfully would require additional HTTP-level authentication to identify
>> users and prevent abuse (as most proxies do).  Restructuring the internet,
>> whether it is adding a new port to unblock, or permitting specific classes
>> of CONNECT traffic, would be a similar battle.
>
> Perhaps more to the point, CONNECT is a method that is only allowed to be
> sent to a client-side proxy server.  Deliberately sending it in other
> HTTP messages would be a violation of its method semantics and the
> HTTP/1.1 syntax (because its unusual target syntax is only allowed
> when sent to a proxy).

That seems like a matter of perspective.  When opening a connection to
a WebSocket server, can one not view the server as a proxy sever?

Adam