On Tue, Dec 8, 2009 at 4:59 PM, Ian Hickson wrote:
> On Tue, 8 Dec 2009, Fumitoshi Ukai (榈~\椋兼~V~G鎫U~O) wrote:
> >
> > protocol now accepts U+0020. Is it ok to use U+0020 only in /protocol/ ?
> > (e.g. new WebSocket("ws://example.com/", " "); )
> > It seems space is optional after colon in field
On Tue, 8 Dec 2009, Fumitoshi Ukai (��~\飼�~V~G�~U~O) wrote:
>
> protocol now accepts U+0020. Is it ok to use U+0020 only in /protocol/ ?
> (e.g. new WebSocket("ws://example.com/", " "); )
> It seems space is optional after colon in field of handshake message, how
> can we distinguish U+0020 and U+
On Mon, Dec 7, 2009 at 7:25 PM, Ian Hickson wrote:
> On Mon, 7 Dec 2009, Fumitoshi Ukai (�µ~\飼æ~V~Gæ~U~O) wrote:
> > On Mon, Dec 7, 2009 at 5:05 PM, Ian Hickson wrote:
> > > On Mon, 7 Dec 2009, Fumitoshi Ukai (榈~\椋兼~V~G鎫U~O) wrote:
> > > > > > >
> > > > > > > Control characters are allowed (thou
On Mon, 7 Dec 2009, Fumitoshi Ukai (��~\飼�~V~G�~U~O) wrote:
> On Mon, Dec 7, 2009 at 5:05 PM, Ian Hickson wrote:
> > On Mon, 7 Dec 2009, Fumitoshi Ukai (榈~\椋兼~V~G鎫U~O) wrote:
> > > > > >
> > > > > > Control characters are allowed (though using them would be
> > > > > > silly).
> > > > >
> > > > >
On Mon, Dec 7, 2009 at 5:05 PM, Ian Hickson wrote:
>
> On Mon, 7 Dec 2009, Fumitoshi Ukai (榈~\椋兼~V~G鎫U~O) wrote:
> > > > >
> > > > > Control characters are allowed (though using them would be silly).
> > > >
> > > > Why are control characters (except LF and CR) allowed?
> > >
> > > There doesn't
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 incompati
On Mon, 7 Dec 2009, Fumitoshi Ukai (��~\飼�~V~G�~U~O) wrote:
> > > >
> > > > Control characters are allowed (though using them would be silly).
> > >
> > > Why are control characters (except LF and CR) allowed?
> >
> > There doesn't seem to be a good reason to exclude them, and excluding
> > them
Hi,
At 1.130 of "The Web Socket API", it adds the sub-protocol name must be an
ASCII string with no U+000A LINE FEED (LF) or U+000D CARRIAGE RETURN (CR)
characters in it.
But "The Web Socket protocol" 3.1 Parsing Web Socket URLs, says
1. If /protocol/ is specified but is either the empty stri
