"Data incorrectly framed by UA" error in FF 4

[mattpardee]

Unsure if this is a firefox-specific problem, an issue with Socket.IO or both, but this is the error I get from Socket.IO (v0.6):

3 Nov 13:14:44 - Data incorrectly framed by UA. Dropping connection

... running FireFox 4 (b6) client running on OS X 10.6. Important to note that this only happens consistently when a session is being disconnected. In other words, note the same timestamp of these two log messages:

3 Nov 13:14:44 - Data incorrectly framed by UA. Dropping connection
3 Nov 13:14:44 - Client 989797834539786 disconnected

In the past with Socket.IO 0.5.3 it was also happening, but infrequently and I couldn't pinpoint the cause, though I suspect it may have been after the client connection was idle for some time - if I was AFK or whatever.

Obviously this isn't an issue when the client connection is intentionally closing - typically that means I'm simply loading up a new page on my server and the client is re-connecting anyway - but if there is some larger issue with Socket.IO perhaps it would cause unintended issues for other users.

[gavinuhma]

I get the same error with Socket.IO 0.6.0 and FireFox 3.6.12

The client will connect and immediately disconnect...

6 Nov 22:06:50 - Initializing client with transport "flashsocket"
6 Nov 22:06:50 - Client 7036751995328814 connected
6 Nov 22:06:51 - Data incorrectly framed by UA. Dropping connection
6 Nov 22:06:51 - Client 7036751995328814 disconnected

Strangely, it only seems to happen if a FF browser is the first client to connect after the node app has started. If FF connects anytime after the first client, or refreshes, it tends to connect properly.

[muratmat]

Same error here: Windows7 64bit, Cygwin 1.7.1, , nodejs 0.2.5, socket.io 0.6.0, IE8
The message is shown when i call a disconnect() from the browser:

socketClient.disconnect();

The error does not raise when (on the same machine) using Chrome: the difference is that socket.io uses flashsocket on IE8 (when the error is shown), and it uses websocket when using Chrome.

Wish my report could help.

[rauchg]

Fixed