IETF Logo Mail Archive

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

John Tamplin <jat@google.com> Tue, 30 August 2011 15:40 UTC

Return-Path: <jat@google.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 7E97B21F8CC7 for <hybi@ietfa.amsl.com>; Tue, 30 Aug 2011 08:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.729
X-Spam-Level:
X-Spam-Status: No, score=-105.729 tagged_above=-999 required=5 tests=[AWL=-0.053, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, 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 ctUr3Lg4K6eA for <hybi@ietfa.amsl.com>; Tue, 30 Aug 2011 08:40:32 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id DE23321F8CD6 for <hybi@ietf.org>; Tue, 30 Aug 2011 08:40:31 -0700 (PDT)
Received: from hpaq6.eem.corp.google.com (hpaq6.eem.corp.google.com [172.25.149.6]) by smtp-out.google.com with ESMTP id p7UFfwIQ004038 for <hybi@ietf.org>; Tue, 30 Aug 2011 08:41:59 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1314718919; bh=Pz31TmAY3LlqNXYoplSGa1mBHf8=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=ma5bCKI1bCFFWHUwVnaq3zWU1iTscDHuQ4/YeMnTfNFn1ma3zb33x1+5ZaNUQIfbx tq0VLtTzThOpZ78PJuJHA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=oBEwjnR24rn5vvSk+U9AFTlDUwOGi1US9V/D68bH9LyVztjXNjmPh2UA9ZQEpiNKV IeBSnaNPQscVsUX3OUwHA==
Received: from gwaa20 (gwaa20.prod.google.com [10.200.27.20]) by hpaq6.eem.corp.google.com with ESMTP id p7UFevhX007955 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <hybi@ietf.org>; Tue, 30 Aug 2011 08:41:57 -0700
Received: by gwaa20 with SMTP id a20so6036050gwa.0 for <hybi@ietf.org>; Tue, 30 Aug 2011 08:41:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=yRvp+SuNtziZ99QsPeAHTPgKaOdOjcDcTjNNhjZw9HQ=; b=F2Ar2gqbCYYoeLlMfCjcQhw4LlPxvQ00KYzoPLPSStsShmK1msA7Gkwk/MsaAQdLIh nyxh+bytF7bnVLuTFlEQ==
Received: by 10.150.48.8 with SMTP id v8mr2445754ybv.401.1314718917247; Tue, 30 Aug 2011 08:41:57 -0700 (PDT)
Received: by 10.150.48.8 with SMTP id v8mr2445746ybv.401.1314718917102; Tue, 30 Aug 2011 08:41:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.49.7 with HTTP; Tue, 30 Aug 2011 08:41:37 -0700 (PDT)
In-Reply-To: <CALiegfmSs-FhS5AuJHWFhGdbxS4pLSHA1Kk2y_P5GwwG_YneyQ@mail.gmail.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>
From: John Tamplin <jat@google.com>
Date: Tue, 30 Aug 2011 11:41:37 -0400
Message-ID: <CABLsOLCBSnW+R9vr=RbRosTo55tv-_gG9yLdoj5AqW4rU6rcPQ@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Content-Type: multipart/alternative; boundary="000e0cd70d3c088b9604abbada54"
X-System-Of-Record: true
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:40:32 -0000

On Tue, Aug 30, 2011 at 7:29 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote:

> 2011/8/30 Alexey Melnikov <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.

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.23.0 | Report a Bug | By Email