Socket.io dies (uncatchable) on faulty web socket connection about socket.io HOT 5 CLOSED

Fix for certain buggy clients. Needs more investigation. Thanks Malte Ubl (@cramforce) for the report. Closed by 701c35d

from socket.io.

Still getting this in 0.5.3.

Here's a copy of the error:
/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/transports/websocket.js:23
this.connection.setTimeout(0);
^
TypeError: Object # has no method 'setTimeout'
at [object Object]._onConnect (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/transports/websocket.js:23:18)
at [object Object]. (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/client.js:17:7)
at new (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/transports/websocket.js:7:9)
at [object Object]._onConnection (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/listener.js:123:73)
at [object Object].check (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/listener.js:83:9)
at Server. (/home/mediadesign/lib/node/.npm/socket.io/0.5.3/package/lib/socket.io/listener.js:39:12)
at Server.emit (events:27:15)
at HTTPParser.onIncoming (http:831:10)
at HTTPParser.onHeadersComplete (http:87:31)
at Stream.ondata (http:763:22)

from socket.io.

FWIW, http://github.com/dshaw/canisocket/ is running with @miksago's node-websocket-server without issue. http://canisocket.com/

Perhaps that will help triangulate the issue.

from socket.io.

It was fixed in master

from socket.io.

Great, thanks Guillermo. Switched to master and http://github.com/dshaw/remoteconsole is working great.

from socket.io.