Client side 'connectTimeout' parameter doesn't work when WebSocket is opened but messages are blocked

[dmitry-treskunov]

From the https://groups.google.com/forum/#!topic/atmosphere-framework/IKkyYlFxlk8:

Usually, the first message sent using WebSocket looks like 40|48d70d7a-ac1b-41c9-b68a-818d0c451bee|0||.

On the javascript side the idea is that connection is opened only when such message is received.

I use 'connectTimeout' parameter and I expect that if the first message was not received in this timeout, then onTransportFailure will be called. But it's not, because (looking through the atmosphere.js code) websocket's onopen callback clears timeout function:

_websocket.onopen = function (message) {
    _timeout(_request);
    ...
};
function _timeout(_request) {
    clearTimeout(_request.id);
    ...
}

It can be reproduced in case of some antivirus, firewall, proxy who allows WS connection, but doesn't pass frames.