IETF Logo Mail Archive

Re: [hybi] Handshake was: The WebSocket protocol issues.

Greg Wilkins <gregw@webtide.com> Thu, 23 September 2010 23:53 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 8830E3A6918 for <hybi@core3.amsl.com>; Thu, 23 Sep 2010 16:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.766
X-Spam-Level:
X-Spam-Status: No, score=-1.766 tagged_above=-999 required=5 tests=[AWL=0.211, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 UzD9oKSw1lZL for <hybi@core3.amsl.com>; Thu, 23 Sep 2010 16:53:04 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 9D66B3A682C for <hybi@ietf.org>; Thu, 23 Sep 2010 16:53:04 -0700 (PDT)
Received: by iwn3 with SMTP id 3so2144408iwn.31 for <hybi@ietf.org>; Thu, 23 Sep 2010 16:53:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.157.205 with SMTP id c13mr2879276ibx.71.1285286014770; Thu, 23 Sep 2010 16:53:34 -0700 (PDT)
Received: by 10.231.178.88 with HTTP; Thu, 23 Sep 2010 16:53:34 -0700 (PDT)
In-Reply-To: <CA566BAEAD6B3F4E8B5C5C4F61710C110FB27C59@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
References: <AANLkTikszM0pVE-0dpZ2kv=i=y5yzS2ekeyZxtz9N=fQ@mail.gmail.com> <CA566BAEAD6B3F4E8B5C5C4F61710C110FB27C59@TK5EX14MBXW605.wingroup.windeploy.ntdev.microsoft.com>
Date: Thu, 23 Sep 2010 16:53:34 -0700
Message-ID: <AANLkTim1GMXZXSJiUW885=YN4pFMJU_AXLiroXtquJVk@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: Gabriel Montenegro <gmonte@microsoft.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: hybi <hybi@ietf.org>, Alexander Voronin <alexander.voronin@gmail.com>
Subject: Re: [hybi] Handshake was: The WebSocket protocol issues.
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: Thu, 23 Sep 2010 23:53:05 -0000

On 23 September 2010 13:48, Gabriel Montenegro <gmonte@microsoft.com> wrote:
> +1 on this handshake. The only comment I'd make is that the server ping does not need to wait for a different message. It can follow the 101, as long as its after the empty line following the 101, as anything at that point is now expected to be websocket protocol and no longer HTTP.


Gabriel,

The intention is to send the ping immediately after the 101 response
without waiting for anything.

> If there's any fear that the server's hash in the ping could collide with any other protocol's payload, then just add "WebSocket" to the hash in the ping.

That hash algorithm works for me.

v2.23.0 | Report a Bug | By Email