IETF Logo Mail Archive

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

Philipp Serafin <phil127@gmail.com> Wed, 31 August 2011 20:07 UTC

Return-Path: <phil127@gmail.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 EFC5C21F8DA7 for <hybi@ietfa.amsl.com>; Wed, 31 Aug 2011 13:07:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.394
X-Spam-Level:
X-Spam-Status: No, score=-3.394 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 OD8VbPPaF9UA for <hybi@ietfa.amsl.com>; Wed, 31 Aug 2011 13:07:33 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3457621F8DA0 for <hybi@ietf.org>; Wed, 31 Aug 2011 13:07:33 -0700 (PDT)
Received: by bkar4 with SMTP id r4so1436328bka.31 for <hybi@ietf.org>; Wed, 31 Aug 2011 13:09:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type; bh=12rBpu14naMOKU8F0U+RvHw+UIeDzMcSZWS9PHXPdKg=; b=G+A4Chw3tjOTbHLFQwKC0e7nVVrjO0QmIrEx5oV69WwceRtS78J7vsfHoWEf35rlVR lP6rkVuZkR6ciJ7I4mhYWRS9vHq4tG4LIt84KqQQ12exiM9Pl/mTSUQz63dukiVkFnDl boctFeaRoPINmUnlcqmEn5WVH+MkQE5AVIyXY=
Received: by 10.204.157.2 with SMTP id z2mr472406bkw.107.1314821340984; Wed, 31 Aug 2011 13:09:00 -0700 (PDT)
Received: from [212.201.70.0] ([212.201.70.0]) by mx.google.com with ESMTPS id zu10sm497731bkb.5.2011.08.31.13.08.59 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Aug 2011 13:09:00 -0700 (PDT)
Message-ID: <4E5E94D8.4070302@gmail.com>
Date: Wed, 31 Aug 2011 22:08:56 +0200
From: Philipp Serafin <phil127@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1
MIME-Version: 1.0
To: Iñaki Baz Castillo <ibc@aliax.net>, Hybi <hybi@ietf.org>
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> <4E5D04F8.30801@isode.com> <4E5E5EDA.6000606@gmail.com> <4E5E79C4.2080100@callenish.com> <CAMaigVkreB5P2ieXJxZbQ3yPZs0kwmJmqvA0t0jHMBA40BjF-Q@mail.gmail.com> <CALiegfmi3et2==qziAg1toWHjkiBAUrLfQDPmEKuU+Jx_D6ZTQ@mail.gmail.com> <CABLsOLC0m-NpG6L-95rju3vLinMa3d8b3pncoM53fkoN+xs3Fg@mail.gmail.com> <CALiegfkYc=S2-Ljc3Tvy+28EjiHSHv5GrDk4aAQi8q=aQjRV1Q@mail.gmail.com>
In-Reply-To: <CALiegfkYc=S2-Ljc3Tvy+28EjiHSHv5GrDk4aAQi8q=aQjRV1Q@mail.gmail.com>
X-Enigmail-Version: 1.3.1
Content-Type: multipart/alternative; boundary="------------080202060703020306050702"
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: Wed, 31 Aug 2011 20:07:34 -0000

Am 31.08.2011 22:05, schrieb Iñaki Baz Castillo:
> Me (and others AFAIK) are just proposing that, in *case* the client
> provides a WS protocol in the HTTP GET, and the server *does not*
> support such protocol, then the server MUST reject the WS handshake
> (which means a 4XX error code rather than "101 I don't know what we
> are supposed to speak now but I accept the WS session").
Exactly.

v2.23.0 | Report a Bug | By Email