Re: [hybi] More feedback on WebSockets

Ian Hickson <ian@hixie.ch> Tue, 27 October 2009 18:36 UTC

Return-Path: <ian@hixie.ch>
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 C8BDC3A6899 for <hybi@core3.amsl.com>; Tue, 27 Oct 2009 11:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level:
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 89-e2PsiUwio for <hybi@core3.amsl.com>; Tue, 27 Oct 2009 11:36:26 -0700 (PDT)
Received: from looneymail-a1.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 1308B3A6831 for <hybi@ietf.org>; Tue, 27 Oct 2009 11:36:26 -0700 (PDT)
Received: from hixie.dreamhostps.com (hixie.dreamhost.com [208.113.210.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by looneymail-a1.g.dreamhost.com (Postfix) with ESMTP id C395B15D7CF; Tue, 27 Oct 2009 11:36:39 -0700 (PDT)
Date: Tue, 27 Oct 2009 18:36:44 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Greg Wilkins <gregw@webtide.com>
In-Reply-To: <4AE6C7D1.30003@webtide.com>
Message-ID: <Pine.LNX.4.62.0910271834480.25616@hixie.dreamhostps.com>
References: <FDC38D4B-AB64-4F6B-B569-81D7A56DEC8D@mnot.net> <Pine.LNX.4.62.0910270912040.9145@hixie.dreamhostps.com> <4AE6C7D1.30003@webtide.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: hybi@ietf.org
Subject: Re: [hybi] More feedback on WebSockets
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, 27 Oct 2009 18:36:26 -0000

On Tue, 27 Oct 2009, Greg Wilkins wrote:
> Ian Hickson wrote:
> > I disagree that the current handshake isn't like HTTP enough, though. 
> > The request is fully HTTP-compliant. What value would there be in 
> > relaxing the rules on what WebSocket clients should send in the 
> > request? I don't understand the real-world case you are concerned 
> > about.
> 
> What about a load balancer in front of the server that inserts a cookie 
> or X-Forwarded-For header into all HTTP requests that it forwards.
> 
> This will probably be harmless with regards to the subsequent WS 
> connection, but it will break the handshake so there will not be a 
> subsequent WS connection.

How do such load balancers handle pipelining?

If they support them, then that means they are almost certainly 
incompatible with WebSocket, as far as I can tell, and we would _want_ the 
connection to fail.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'