Browsers can not fallback from websocket

[Vitaly Puzrin]

We have report from one person, who works behind corporate proxy. When he open our site from IE9 - everything is ok. But when he try opera/chrome/ff, then message bus does not starts.

The only difference, that i see - IE9 does not support websockets, and start with polling directly. Other browsers starts with websockets and then fails. We did log on serverside, but there are no exceptions, related to broken data from that client (searched both IP and timestamp). In firebug there are message "Firefox can't establish connection to server at ws://fontello.com/faye", and nothing more.

Any thoughts, how can it happen and how to debug? I don't like idea to disable websocket transport - only one person from hundreds have such problem. But we can't ignore him.

[James Coglan]

I've mentioned this in the bug thread here: https://github.com/faye/faye/issues/143 but will repeat.

Change this file: https://github.com/faye/faye/blob/master/javascript/transport/web_socket.js

Add code to it to find out:

Which events out of onopen, onerror, onclose fire?

What order to they fire in?

How long is it before you can an error/close event, if any?

These will help determine how we can spot 'late' failures where the socket appears to be open but still doesn't work.

[ixti]

Thanks for your reply I'll make'n'apply patch today and will update an issue #143.

[Vitaly Puzrin]

James, sorry for long silence. We'll do requested debug in nearest days, as soon as close more urgent issues.

As temporary solution, we've tryed SSL via stunnel. It fixed problems with proxies.

вторник, 5 июня 2012 г., 20:45:25 UTC+4 пользователь James Coglan написал: