Re: [hybi] Comments about draft-13

Iñaki Baz Castillo <ibc@aliax.net> Tue, 06 September 2011 12:26 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 3B0E421F85AA for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 05:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.645
X-Spam-Level:
X-Spam-Status: No, score=-2.645 tagged_above=-999 required=5 tests=[AWL=0.032, 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 OkNfvToPJXjB for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 05:26:37 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id A3B2E21F85A1 for <hybi@ietf.org>; Tue, 6 Sep 2011 05:26:37 -0700 (PDT)
Received: by qyk35 with SMTP id 35so3742280qyk.10 for <hybi@ietf.org>; Tue, 06 Sep 2011 05:28:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.221.21 with SMTP id ia21mr738185qcb.253.1315312103318; Tue, 06 Sep 2011 05:28:23 -0700 (PDT)
Received: by 10.229.79.207 with HTTP; Tue, 6 Sep 2011 05:28:23 -0700 (PDT)
In-Reply-To: <CALiegfkUMDfuRC+16ZcLo__2OqAcQ1UVDGa_610ykEAe6yZViw@mail.gmail.com>
References: <CALiegfkUMDfuRC+16ZcLo__2OqAcQ1UVDGa_610ykEAe6yZViw@mail.gmail.com>
Date: Tue, 06 Sep 2011 14:28:23 +0200
Message-ID: <CALiegf=wO6w5UMLO-hsn8o0cX3__SuxMDrgqvScuS6QWdNhptw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: hybi@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [hybi] Comments about draft-13
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: Tue, 06 Sep 2011 12:26:38 -0000

2011/9/2 Iñaki Baz Castillo <ibc@aliax.net>:
> 3) Section 4.2.2 does include nothing about a 4XX HTTP response code
> for the case in which the WS clients offers N WS subprotocols and the
> server supports no one of them. Current text states that the server
> MUST reply 101 without Sec-WebSocket-Protocol, so the client would
> then MUST Fail_The_Connection.
>
> There has been a long thread recently suggesting that in that case
> (and just in *that* case) the server whould *reject* the GET request
> with a *specific* HTTP status code which would mean "I don't support
> any of your suggested WS protocols, so I cannot accept the WS session
> because I have no idea what we are supposed to speak".
>
> This is a new protocol, so feel *free* to create a new "HTTP" response
> code for this case, maybe:
>
>  488 WebSocket SubProtocol Not Supported
>
> As I explained in other thread, this status code could help the human
> user and the client application developer to realize that his software
> is not up-to-date with the service requeriments ("your programm is too
> old, upgrade please").


Hi, any new consideration about this?
Thanks a lot.



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