IETF Logo Mail Archive

Re: [hybi] Comments about draft-13

"Richard L. Barnes" <rbarnes@bbn.com> Tue, 06 September 2011 17:41 UTC

Return-Path: <rbarnes@bbn.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 AA0C521F8B8E for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 10:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.4
X-Spam-Level:
X-Spam-Status: No, score=-106.4 tagged_above=-999 required=5 tests=[AWL=-0.101, BAYES_00=-2.599, 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 Zo6H4ctUiFzt for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 10:41:07 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 3931B21F8B70 for <hybi@ietf.org>; Tue, 6 Sep 2011 10:41:07 -0700 (PDT)
Received: from ros-dhcp192-1-51-76.bbn.com ([192.1.51.76]:61775) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1R0zfi-000LTV-6L; Tue, 06 Sep 2011 13:42:54 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <CALiegfnjXqggJhZG2YHSAQLK+uPXTxyKo3N=K4qE6OdjwieNtg@mail.gmail.com>
Date: Tue, 06 Sep 2011 13:42:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AADB2126-0259-4636-88D8-78D8B5E69EE6@bbn.com>
References: <CALiegfkUMDfuRC+16ZcLo__2OqAcQ1UVDGa_610ykEAe6yZViw@mail.gmail.com> <CALiegf=wO6w5UMLO-hsn8o0cX3__SuxMDrgqvScuS6QWdNhptw@mail.gmail.com> <A59BAA80-CD38-48C4-A113-C1493072D079@bbn.com> <CALiegfnru1MDVLZAQW9cxrR4D=Wfu+MAEzn0BHfSu_v31ztvrg@mail.gmail.com> <CALiegfnjXqggJhZG2YHSAQLK+uPXTxyKo3N=K4qE6OdjwieNtg@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
X-Mailer: Apple Mail (2.1084)
Cc: hybi@ietf.org
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 17:41:07 -0000

Hence the "pretty much" :)  

One could argue that scripts can also set the Content-Length header as well, by setting the length of a message.  But the current WS API offers a much more direct channel to Websocket-Protocol, allowing the script to put in arbitrary strings.

--Richard


On Sep 6, 2011, at 1:40 PM, Iñaki Baz Castillo wrote:

> 2011/9/6 Iñaki Baz Castillo <ibc@aliax.net>:
>> 2011/9/6 Richard L. Barnes <rbarnes@bbn.com>:
>>> Also, to re-iterate a comment I made earlier, "Sec-Websocket-Protocol" should just be "Websocket-Protocol", since it is not "Sec" -- scripts can set the value pretty much directly.
>> 
>> +1
> 
> Well, scripts can set the value pretty much directly but at least
> JavaScript API for WebSocket requires such a value to be an string or
> an array of strings. I expect that a JS code cannot set binary or
> custom value in "Sec-Websocket-Protocol" header.
> 
> 
> 
> -- 
> Iñaki Baz Castillo
> <ibc@aliax.net>

v2.23.0 | Report a Bug | By Email