On 2011-07-12 09:48, Iñaki Baz Castillo wrote:
2011/7/12 Mykyta Yevstifeyev<evnikita2(_at_)gmail(_dot_)com>:
Sec-WebSocket-Extensions: bar; baz=2
is exactly equivalent to
Sec-WebSocket-Extensions: foo, bar; baz=2
These two examples don't match the aforementioned ABNF; the space before
"baz=2" should be removed.
Hi, are you sure of that? In SIP protocol (which inherits from HTTP
grammar) a header parameter (;foo=lalala) can contain spaces anywhere
(before/after the ";", before/after the "="). So something like:
Sec-WebSocket-Extensions: foo , bar ; baz = 2
is valid.
However it's not clear for me wheter in this example "baz=2" is a
header param or a param just for the value "bar". In the last case it
would mean a specific header syntax, so spaces could be not allowed.
Could you please point to the ABNF grammar you meant?
According to
<http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-10#section-9.1>
it's a parameter of "bar".
That being said, I'm not happy with
extension-param = token [ "=" token ]
In HTTP header fields, parameters usually support both token and
quoted-string form.
Making this special means that existing header field parser code can't
be easily re-used.
Best regards, Julian
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf