Re: [hybi] Multiplexing extension spec draft 03

[Julian Reschke <[e-mail]>]

On 2012-02-28 18:41, Tobias Oberstein 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? 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?

<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.4.2p.5>

"Multiple message-header fields with the same field-name MAY be present 
in a message if and only if the entire field-value for that header field 
is defined as a comma-separated list [i.e., #(values)]. It MUST be 
possible to combine the multiple header fields into one "field-name: 
field-value" pair, without changing the semantics of the message, by 
appending each subsequent field-value to the first, each separated by a 
comma. The order in which header fields with the same field-name are 
received is therefore significant to the interpretation of the combined 
field value, and thus a proxy MUST NOT change the order of these field 
values when a message is forwarded."

But that doesn't necessarily mean it's a good idea.

Best regards, Julian