Re: [hybi] Intermediaries and idle connections (was Re: Technical feedback.)

Greg Wilkins <gregw@webtide.com> Sun, 31 January 2010 00:43 UTC

Return-Path: <gregw@webtide.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 35CCF3A683F for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 16:43:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level:
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[AWL=0.189, BAYES_00=-2.599]
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 WT7mBlvnIg91 for <hybi@core3.amsl.com>; Sat, 30 Jan 2010 16:42:59 -0800 (PST)
Received: from mail-yx0-f194.google.com (mail-yx0-f194.google.com [209.85.210.194]) by core3.amsl.com (Postfix) with ESMTP id 6A4E23A67A8 for <hybi@ietf.org>; Sat, 30 Jan 2010 16:42:59 -0800 (PST)
Received: by yxe32 with SMTP id 32so34146yxe.5 for <hybi@ietf.org>; Sat, 30 Jan 2010 16:43:24 -0800 (PST)
Received: by 10.101.129.23 with SMTP id g23mr3204854ann.5.1264898604398; Sat, 30 Jan 2010 16:43:24 -0800 (PST)
Received: from ?10.10.1.11? (60-242-119-126.tpgi.com.au [60.242.119.126]) by mx.google.com with ESMTPS id 15sm2210691gxk.12.2010.01.30.16.43.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 30 Jan 2010 16:43:23 -0800 (PST)
Message-ID: <4B64D221.1000603@webtide.com>
Date: Sun, 31 Jan 2010 11:43:13 +1100
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Justin Erenkrantz <justin@erenkrantz.com>, "hybi@ietf.org" <hybi@ietf.org>
References: <de17d48e1001280012i2657b587i83cda30f50013e6b@mail.gmail.com> <Pine.LNX.4.64.1001291134350.22020@ps20323.dreamhostps.com> <4B62E516.2010003@webtide.com> <5c902b9e1001290756r3f585204h32cacd6e64fbebaa@mail.gmail.com> <4B636757.3040307@webtide.com> <E379EA13-D58A-4BFB-A62D-2B931A54E276@apple.com> <4B63DD6B.5030803@webtide.com> <E765982E-06B5-48BC-B75D-02E3F9555018@apple.com> <4B64B179.9050502@webtide.com> <2D6C6FEE-2019-44E4-BD82-7BF68B30A518@apple.com> <5c902b9e1001301637q27028696o8ca9220c52a235e1@mail.gmail.com>
In-Reply-To: <5c902b9e1001301637q27028696o8ca9220c52a235e1@mail.gmail.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [hybi] Intermediaries and idle connections (was Re: Technical feedback.)
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: Sun, 31 Jan 2010 00:43:00 -0000

Justin Erenkrantz wrote:

> On the server side, I can't even begin to think of the contortions
> we'd have to add to httpd to get it to recognize a specific byte
> pattern *on port 80*.  

The difficulty on the server side is that you don't even know it
is a websocket upgrade request until you have already parsed
it (using the lenient parsers that most HTTP servers have).

So you then have to re-parse it to check the exact byte order!

cheers