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 11:24 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 A3D6821F8C1E for <hybi@ietfa.amsl.com>; Tue, 30 Aug 2011 04:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.696
X-Spam-Level:
X-Spam-Status: No, score=-101.696 tagged_above=-999 required=5 tests=[AWL=-0.793, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396, 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 nRjc8awefxFY for <hybi@ietfa.amsl.com>; Tue, 30 Aug 2011 04:24:24 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id DA7D521F8C1D for <hybi@ietf.org>; Tue, 30 Aug 2011 04:24:23 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TlzIvgBpJmOA@rufus.isode.com>; Tue, 30 Aug 2011 12:25:50 +0100
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4E5CC8B8.7090702@isode.com>
Date: Tue, 30 Aug 2011 12:25:44 +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: Iñaki Baz Castillo <ibc@aliax.net>
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>
In-Reply-To: <CALiegfnc-YRPZZvgJjmvtafKnkJB7rXJ9KcPDKL-ceeAdwGEGQ@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 11:24:24 -0000

Iñaki Baz Castillo wrote:

>2011/8/30 Alexey Melnikov <alexey.melnikov@isode.com>:
>  
>
>>>Why should the WS server accept (so 101) a WS handshake when the
>>>client offers WS protocols NOT supported by the WS server? I don't
>>>mean that the client does not provide Sec-WebSocket-Protocol header, I
>>>mean that the client *provides * it, but offered protocols are NOT
>>>supported by the server.
>>>      
>>>
>>Because by definition the list of extensions in the Sec-WebSocket-Protocol
>>header field is optional for the server to support. If we want to have "you
>>must support this extension, or we fail the handshake", then we need another
>>mechanism to tell the server.
>>    
>>
>Ok, so after client offers "Sec-WebSocket-Protocol: aaa, bbb" and the
>server provides NO such header in the 101 response.... what are client
>and server supposed to speak now?
>  
>
If the client really expected the extensions to be mandatory, it has to 
send Close.

v2.23.0 | Report a Bug | By Email