IETF Logo Mail Archive

Re: [hybi] Multiplexing extension spec draft 03

Tobias Oberstein <tobias.oberstein@tavendo.de> Tue, 28 February 2012 17:41 UTC

Return-Path: <tobias.oberstein@tavendo.de>
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 485ED21F8613 for <hybi@ietfa.amsl.com>; Tue, 28 Feb 2012 09:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 qMK7BLDn4ysA for <hybi@ietfa.amsl.com>; Tue, 28 Feb 2012 09:41:09 -0800 (PST)
Received: from EXHUB020-5.exch020.serverdata.net (exhub020-5.exch020.serverdata.net [206.225.164.32]) by ietfa.amsl.com (Postfix) with ESMTP id 4B09421F85F6 for <hybi@ietf.org>; Tue, 28 Feb 2012 09:41:09 -0800 (PST)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.228]) by EXHUB020-5.exch020.serverdata.net ([206.225.164.32]) with mapi; Tue, 28 Feb 2012 09:41:08 -0800
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: "hybi@ietf.org" <hybi@ietf.org>
Date: Tue, 28 Feb 2012 09:41:05 -0800
Thread-Topic: [hybi] Multiplexing extension spec draft 03
Thread-Index: Acz2OJ1dqU9DQLZbQBqArGB9riMPzAABoNYw
Message-ID: <634914A010D0B943A035D226786325D42D5992F76E@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJb1ewPO3EBgD78anD+=4XouToGR4X7C1wvWqonc2nYB6g@mail.gmail.com>
In-Reply-To: <CAH9hSJb1ewPO3EBgD78anD+=4XouToGR4X7C1wvWqonc2nYB6g@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [hybi] Multiplexing extension spec draft 03
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, 28 Feb 2012 17:41:10 -0000

>>- Now the order of extensions in Sec-WebSocket-Extensions determines where those extensions are applied to frames (before or after (de)multiplexing)

Huh. _Order is significant_ ??

Is that even supported by the WS base spec? If so, is there precedence with other HTTP headers introducing order sign.?

Somehow I feel uncomfortable with introducing order sign. in a header .. 

And what if Sec-WebSocket-Extensions header appears more than once (don't remember right now
if thats allowed for that specific header)? If so, aren't intermediaries allowed to reorder headers?

v2.23.0 | Report a Bug | By Email