Re: [hybi] Sec-WebSocket-Extensions field spec. contradiction

[Alexey Melnikov <[e-mail]>]

Iñaki Baz Castillo wrote:

>2011/9/3 Sylvain Hellegouarch <[e-mail]>:
>  
>
>>Section 4.2.2 says:
>>    
>>
>>>If multiple extensions are to be used, they must all be listed in a single
>>>Sec-WebSocket-Extensions header field.  This header field MUST NOT be
>>>repeated.
>>>      
>>>
>>But section 9.1 says:
>>
>>    
>>
>>>Note that like other HTTP header fields, this header field MAY be split or
>>>combined across multiple lines.  Ergo, the following are equivalent:
>>>        Sec-WebSocket-Extensions: foo
>>>        Sec-WebSocket-Extensions: bar; baz=2
>>>is exactly equivalent to
>>>        Sec-WebSocket-Extensions: foo, bar; baz=2
>>>      
>>>
>>Aren't those two statements contradicting themselves?
>>    
>>
Yes, this is a bug.

>Good point. Also, why couldn't such a header occur multiple times in a
>HTTP request/response? Usually, any HTTP header allowing multivalue
>(separated by comma) also allows different values across multiple
>headers, so:
>
>  Foo: qwe, asd
>  Foo:  zxc
>
>is the same as:
>
>  Foo: qwe, asd, zxc
>
>
>This is true for most of the HTTP headers and parsers MUST be ready
>for that. Please, don't add artificial constraints.
>  
>
Any other comments on this? I will implement this change unless there 
are some objections.