IETF Logo Mail Archive

Re: [hybi] WebSocket -76 is incompatible with HTTP reverse proxies

Greg Wilkins <gregw@webtide.com> Mon, 26 July 2010 01:05 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 F24983A680C for <hybi@core3.amsl.com>; Sun, 25 Jul 2010 18:05:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.742
X-Spam-Level:
X-Spam-Status: No, score=-1.742 tagged_above=-999 required=5 tests=[AWL=0.234, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 zURrqPe4L3fM for <hybi@core3.amsl.com>; Sun, 25 Jul 2010 18:05:38 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id C06BC3A67EC for <hybi@ietf.org>; Sun, 25 Jul 2010 18:05:37 -0700 (PDT)
Received: by fxm1 with SMTP id 1so6470202fxm.31 for <hybi@ietf.org>; Sun, 25 Jul 2010 18:05:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.122.195 with SMTP id m3mr5639716far.86.1280106357839; Sun, 25 Jul 2010 18:05:57 -0700 (PDT)
Received: by 10.223.112.129 with HTTP; Sun, 25 Jul 2010 18:05:57 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1007222024430.7242@ps20323.dreamhostps.com>
References: <068.da8db0c773647cb0ed73d576f39e93ee@tools.ietf.org> <20100717023749.GA2426@shareable.org> <AANLkTil36SNqlpqq2zNMVSgsA_27kqnuioi0qFTKQR1m@mail.gmail.com> <20100721223010.GB14589@shareable.org> <20100721223947.GD6475@1wt.eu> <Pine.LNX.4.64.1007222024430.7242@ps20323.dreamhostps.com>
Date: Mon, 26 Jul 2010 11:05:57 +1000
Message-ID: <AANLkTik1V0MQTuSoOgachG+MwU8BdW+_CXe4iuisVr0M@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary="001636c5b142bbd889048c3ffcf1"
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] WebSocket -76 is incompatible with HTTP reverse proxies
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: Mon, 26 Jul 2010 01:05:40 -0000

On 23 July 2010 06:44, Ian Hickson <ian@hixie.ch> wrote:



> As long as the server has not responded with 101, it *IS* HTTP.

I disagree with the premise of this statement.
>

This is the road block that we have come up against for month after month
after month.

I think we have to assume that you are unconvincing that the handshake MUST
be HTTP compliant before the 101. But can you explain why you think that it
MUST be HTTP non-compliant before the 101?

Why can't we just make it HTTP compliant before the 101 so it will get us
past this road block.  What are the problems that result from doing this?
Surely you can give us the chance to address them by other means than by
being HTTP non-compliant?

v2.23.0 | Report a Bug | By Email