Re: [hybi] Yet more additional WebSocket Close Error Codes

Jason Duell <jduell.mcbugs@gmail.com> Fri, 18 May 2012 23:36 UTC

Return-Path: <jduell.mcbugs@gmail.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BF8421F85DF for <hybi@ietfa.amsl.com>; Fri, 18 May 2012 16:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.854
X-Spam-Level:
X-Spam-Status: No, score=-2.854 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FndEJ5dkjkPO for <hybi@ietfa.amsl.com>; Fri, 18 May 2012 16:36:29 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 985E121F85D6 for <hybi@ietf.org>; Fri, 18 May 2012 16:36:22 -0700 (PDT)
Received: by qcsq13 with SMTP id q13so2804111qcs.31 for <hybi@ietf.org>; Fri, 18 May 2012 16:36:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=LwIy5oHi9jeT/TX0L12gO1o8Qw8IpjxxK8vkHYGXzvg=; b=f7bkuWPp9Xg0wEG04MJQvnOGz6in2UfvRwxmv3D4KvJmPude7sTKRBgI9rbeY0ExU3 3HKYcE4ohk1OI8FeQ0DqNSo8m5swKPKyu6zi/qZJrpbUYBk3V64rhNIBd7f2lncMQdzJ rbxFe6D3++jeTufYbHkeLVlZhU68nl/YqtmxbSfRlwnHU8YRJ2+6hcAoiFqbf5lZ6Cgu PcjHr4KRHnXVQvTxWImKffPmOIblHPZk+3oP+ZeMWgzwUnok5w/9WQE80x4xM10nE68r kGP5y/kCbjaaYC4qOPkvmaf1Z+/AfTRqjFJzQWiMvQ89d/+y5tFRQCsCR/szJfjYu2d8 hgLQ==
Received: by 10.224.217.9 with SMTP id hk9mr26060263qab.59.1337384182126; Fri, 18 May 2012 16:36:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.198.26 with HTTP; Fri, 18 May 2012 16:36:01 -0700 (PDT)
In-Reply-To: <CAM6mnzK0aOwzKUa=Np512MkOf7m6fJOUHdecK9YZat=vT9iP+w@mail.gmail.com>
References: <CAM6mnzJQTLxztd+6CTugRoONKiHNn-MDTJutPBoCtFUNnfBohQ@mail.gmail.com> <4FB62A69.4040604@gmx.de> <CAM6mnzK0aOwzKUa=Np512MkOf7m6fJOUHdecK9YZat=vT9iP+w@mail.gmail.com>
From: Jason Duell <jduell.mcbugs@gmail.com>
Date: Fri, 18 May 2012 16:36:01 -0700
Message-ID: <CAM6mnzLiYX9mZ-GwvfbLUafjBsvbng8pK=pGG3JmiiDveqyR1g@mail.gmail.com>
To: hybi@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [hybi] Yet more additional WebSocket Close Error Codes
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 18 May 2012 23:36:30 -0000

>>> Chrome is not calling onerror for this, so we have a difference here.
>>> The language in the spec isn't really clear if this covers the
>>> connection-never-happened case.
>>
>> I think it is;

Perhaps you were referring to

"If the establish a WebSocket connection algorithm fails, it triggers
the fail the WebSocket connection algorithm, which then invokes the
close the WebSocket connection algorithm."

That clearly implies onerror should be called when the remote server
connection fails.

It looks like Chromium is going to change to call onerror here too:

  http://code.google.com/p/chromium/issues/detail?id=128057

But: I still don't see any clear language in either spec on what error
code should be used, and think that this is a common enough case to
merit it's own code, or at least clearer language that 1006 should be
used.

Jason