IETF Logo Mail Archive

Re: [hybi] WS close code equivalent to HTTP 500/Internal Server Error

Iñaki Baz Castillo <ibc@aliax.net> Sat, 08 October 2011 20:46 UTC

Return-Path: <ibc@aliax.net>
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 2EA9F21F8B32 for <hybi@ietfa.amsl.com>; Sat, 8 Oct 2011 13:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 UlS5U2tQ6g4E for <hybi@ietfa.amsl.com>; Sat, 8 Oct 2011 13:46:37 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9680621F87FA for <hybi@ietf.org>; Sat, 8 Oct 2011 13:46:37 -0700 (PDT)
Received: by vcbfo11 with SMTP id fo11so4795708vcb.31 for <hybi@ietf.org>; Sat, 08 Oct 2011 13:49:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.120.12 with SMTP id b12mr971772vcr.111.1318106993545; Sat, 08 Oct 2011 13:49:53 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Sat, 8 Oct 2011 13:49:53 -0700 (PDT)
In-Reply-To: <02F41063-6221-4EB8-A4E4-2E396A6B946C@zaphoyd.com>
References: <02F41063-6221-4EB8-A4E4-2E396A6B946C@zaphoyd.com>
Date: Sat, 08 Oct 2011 22:49:53 +0200
Message-ID: <CALiegfkA4DdnwWVBgATgP7tq03nBpUE-pWkeYnKtOyEQS+bELA@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Peter Thorson <webmaster@zaphoyd.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: hybi@ietf.org
Subject: Re: [hybi] WS close code equivalent to HTTP 500/Internal Server Error
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: Sat, 08 Oct 2011 20:46:38 -0000

2011/10/7 Peter Thorson <webmaster@zaphoyd.com>:
> Browsers only report the status code itself and not the reason

The WS API tells you the status code and the reason (when present) of
the closure.


> so sending a normal/going away error code with a more specific reason is less helpful. What are other implementations doing in this case? Would another close code for internal server error make sense?

Good question :)



-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email