Re: [hybi] failed TLS handshake: which close code?

[Tobias Oberstein <[e-mail]>]

> To quote the WebSocket API:
> "
> If the user agent was required to fail the websocket connection or the
> WebSocket connection is closed with prejudice, fire a simple event named
> error at the WebSocket object.
> "
> 
> So if TLS fails and the client has to _Fail the WebSocket Connection_, then
> the API only reports an error; it does not provide a close code.  Which is
> appropriate, because the existence of a close code presumes the existence
> of an established WS connection, which does not exist in this case.
> 

But the text of above (step 2) spec continues (with step 3):

"
Create an event that uses the CloseEvent interface, with the event name close, which does not bubble, is not cancelable, has no default action, whose wasClean attribute is initialized to true if the connection closed cleanly and false otherwise, whose code attribute is initialized to the WebSocket connection close code, and whose reason attribute is initialized to the WebSocket connection close reason decoded as UTF-8, with error handling, and dispatch the event at the WebSocket object.
"

I'm not sure: does step 2 prevent doing step 3?

In any case:

a) Firefox currently fires "close" with 1006 "Abormal Close" on TLS invalid cert. failure

b) If no WS close code will be reserved for "TLS invalid cert", then what alternative is there to signal that specific error condition to the app?

c) Why is it so bad to have a code never used on wire, but used to signal an error that happened before a WS connection was established?