IETF Logo Mail Archive

Re: [hybi] Multiplexing extension spec draft 03

Takeshi Yoshino <tyoshino@google.com> Tue, 28 February 2012 19:01 UTC

Return-Path: <tyoshino@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 5DBE221F86C7 for <hybi@ietfa.amsl.com>; Tue, 28 Feb 2012 11:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.946
X-Spam-Level:
X-Spam-Status: No, score=-102.946 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 zcA1hjl4gLmg for <hybi@ietfa.amsl.com>; Tue, 28 Feb 2012 11:01:19 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 180DC21F86AD for <hybi@ietf.org>; Tue, 28 Feb 2012 11:01:18 -0800 (PST)
Received: by yhpp34 with SMTP id p34so1243683yhp.31 for <hybi@ietf.org>; Tue, 28 Feb 2012 11:01:18 -0800 (PST)
Received-SPF: pass (google.com: domain of tyoshino@google.com designates 10.236.174.106 as permitted sender) client-ip=10.236.174.106;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of tyoshino@google.com designates 10.236.174.106 as permitted sender) smtp.mail=tyoshino@google.com; dkim=pass header.i=tyoshino@google.com
Received: from mr.google.com ([10.236.174.106]) by 10.236.174.106 with SMTP id w70mr30111747yhl.68.1330455678709 (num_hops = 1); Tue, 28 Feb 2012 11:01:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=xX+EDLTfCEkOsSobGMBaq2VBXabOF0OH1GTvUjluzdw=; b=1BE4IjJytzhd2VjPK+9Y9c4VUQYesyDmFgda0gWSorHmIdglUkDKB/uzOx75EqPcpU f7fnjMLQF+iTlzAWZ9iHX+thpf7kkoiLH4lJZUCvRZDdsFqiqXe8HmgjZsn5dagvq+2j W7TxRoVtF97TqL+IvuVfN2gT0DChWBiuI9Ncg=
Received: by 10.236.174.106 with SMTP id w70mr22834205yhl.68.1330455678590; Tue, 28 Feb 2012 11:01:18 -0800 (PST)
Received: by 10.236.174.106 with SMTP id w70mr22834187yhl.68.1330455678436; Tue, 28 Feb 2012 11:01:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.101.155.5 with HTTP; Tue, 28 Feb 2012 11:00:58 -0800 (PST)
In-Reply-To: <634914A010D0B943A035D226786325D42D5992F76E@EXVMBX020-12.exch020.serverdata.net>
References: <CAH9hSJb1ewPO3EBgD78anD+=4XouToGR4X7C1wvWqonc2nYB6g@mail.gmail.com> <634914A010D0B943A035D226786325D42D5992F76E@EXVMBX020-12.exch020.serverdata.net>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Tue, 28 Feb 2012 14:00:58 -0500
Message-ID: <CAH9hSJbd2MrqABaX+fme0MEpPSKtwJNtxyi_iz3RNnEx1a6Mvw@mail.gmail.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: multipart/alternative; boundary="20cf3040e3bc1a48b104ba0ada7c"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQkQUvV+GnF7H+bcpF9yIhPweuRsIG1SVzb4Rvo1hMWaJy0by2Plmxx/wqpKhPXF43PVfZRb3EsImBiZW2L2A4z62Ue4IAzg7DSWmHKnsxz6vlsKXvvzRdom/QEndmbeufi3WnnG
Cc: "hybi@ietf.org" <hybi@ietf.org>
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 19:01:20 -0000

On Tue, Feb 28, 2012 at 12:41, Tobias Oberstein <tobias.oberstein@tavendo.de
> wrote:

> >>- 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?


Yes, as noted in http://tools.ietf.org/html/rfc6455#section-9.1


> If so, is there precedence with other HTTP headers introducing order sign.?
>

What kind of HTTP headers are you worrying about?


>
> 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?
>
>
As described in RFC 6455 p48.

HTTP (RFC 2616) also prohibits reordering such multiple header entries. See
the section 4.2 Message Headers.

v2.23.0 | Report a Bug | By Email