[whatwg] WebSocket sub protocol name.

Ian Hickson wrote:
> ...
>> And, why is it limited to ASCII instead of UTF-8?
> 
> Because the HTTP working group refuse to allow UTF-8 in HTTP headers for 
> reasons that I don't really understand, and the handshake is supposed to 
> be valid HTTP.
> ...

A change of the default encoding would be incompatible with HTTP/1.1.

> On Mon, 7 Dec 2009, Julian Reschke wrote:
>> There isn't a good reason to disallow control characters in a *name*????
> 
> Not as far as I can tell, no... what would a good reason be?

Consistency with every other single spec on the planet with respect to 
names?

Best regards, Julian

Received on Monday, 7 December 2009 00:45:56 UTC