[hybi] Yet more additional WebSocket Close Error Codes

[Jason Duell <[e-mail]>]

I'm wondering if there are two more close codes that would be useful,
to indicate

  1) remote server not reachable

  2) client/browser has too many websockets open already (try later)

Re: #1: Both Web Socket specs are a little vague IMO on how JS is
notified when the targeted web socket server is down/nonexistent/etc.

Firefox is firing an 'error' event when this happens, based AFAICT on
the language here in the W3C spec:

  "if the status code received from the server is not 101 (e.g. it is
a redirect), the user agent must fail the websocket connection"

Chrome is not calling onerror for this, so we have a difference here.
The language in the spec isn't really clear if this covers the
connection-never-happened case.

Both Chrome and Firefox (haven't tested other browsers/clients) are
then calling close with code=1006, which seems the best code available
in RFC 6455, but the language there isn't great either:

   "to indicate that the connection was closed abnormally, e.g.,
without sending or receiving a Close control frame."

Of course the connection wasn't actually "closed" at all, normally or
not. There's essentially no mention in either spec of what happens
when there never was any connection to the server..

It would be useful to be clear about whether onerror should be called
here.   I'm also wondering if it would be useful to have a dedicated
error code for this case ("server not available').

Re: #2: I expect every browser that implements websockets will have
some limit on the number of websockets it allows to be open at once
(to prevent DoS attacks if nothing else).    I'm not sure of what the
right close code for this is.  Ideas?  Perhaps we could also use a
dedicated code for this case too.

Jason Duell
Mozilla