Message not received if close event occurs in client.

[mindspank]

I'm connecting to a websocket server, if for some reason authentication is not valid the server will send a single message stating where to go authenticate and then close the socket.

My issue is that it seems the close event in ws is firing before that message is delivered to the message event listener so I'm missing the message.

In Chromes WS implementation, the frame arrives correctly and then the socket is closed.
In WS client implementation the socket closes immediately and the message event handler is never called.

[lpinca]

Can you try with ws@beta and see if the issue persists?
The bug description is a bit vague but maybe this is a duplicate of #799.

Thanks.

[lpinca]

Closing due to inactivity.