IETF Logo Mail Archive

Re: [hybi] Client offers invalid WS protocols, what must the server do? 101???

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 30 August 2011 15:41 UTC

Return-Path: <alexey.melnikov@isode.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 7246E21F8781 for <hybi@ietfa.amsl.com>; Tue, 30 Aug 2011 08:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level:
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1ST5v+yFMDPL for <hybi@ietfa.amsl.com>; Tue, 30 Aug 2011 08:41:27 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id AC39A21F877B for <hybi@ietf.org>; Tue, 30 Aug 2011 08:41:27 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <Tl0E=gBpJp9q@rufus.isode.com>; Tue, 30 Aug 2011 16:42:54 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4E5D04F8.30801@isode.com>
Date: Tue, 30 Aug 2011 16:42:48 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: John Tamplin <jat@google.com>
References: <CALiegfkC9dLOnLfSQApE9OjoSV1RXT7cTumZ6+yCR1tWo_cvmw@mail.gmail.com> <4E5CBEA0.2080605@isode.com> <CALiegfn3dPyZMR3ZZ3CtwOeAmC4sxd0=kos4Z82B2qeh_aZASQ@mail.gmail.com> <4E5CC6A7.7030304@isode.com> <CALiegfnc-YRPZZvgJjmvtafKnkJB7rXJ9KcPDKL-ceeAdwGEGQ@mail.gmail.com> <4E5CC8B8.7090702@isode.com> <CALiegfmSs-FhS5AuJHWFhGdbxS4pLSHA1Kk2y_P5GwwG_YneyQ@mail.gmail.com> <CABLsOLCBSnW+R9vr=RbRosTo55tv-_gG9yLdoj5AqW4rU6rcPQ@mail.gmail.com>
In-Reply-To: <CABLsOLCBSnW+R9vr=RbRosTo55tv-_gG9yLdoj5AqW4rU6rcPQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-transfer-encoding: quoted-printable
Cc: hybi@ietf.org
Subject: Re: [hybi] Client offers invalid WS protocols, what must the server do? 101???
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, 30 Aug 2011 15:41:28 -0000

John Tamplin wrote:

> On Tue, Aug 30, 2011 at 7:29 AM, Iñaki Baz Castillo <ibc@aliax.net 
> <mailto:ibc@aliax.net>> wrote:
>
>     2011/8/30 Alexey Melnikov <alexey.melnikov@isode.com
>     <mailto:alexey.melnikov@isode.com>>:
>     > If the client really expected the extensions to be mandatory, it
>     has to send
>     > Close.
>
>     A new close status code just to say "the WS protocol negotiation has
>     obviously failed so I close the connection"?
>
>
> We don't need a separate close code for every possible reason -- there 
> will be too many, and we will certainly miss many ones that would 
> actually be used.  Instead, we need more generic error codes 
> describing categories of failures.

I think we need both. More specific error codes are better, if 
introduced early.

v2.23.0 | Report a Bug | By Email