-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Socket.io dies (uncatchable) on faulty web socket connection #44
Comments
Fix for certain buggy clients. Needs more investigation. Thanks Malte Ubl (@cramforce) for the report. Closed by 701c35d |
Still getting this in 0.5.3. Here's a copy of the error: |
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. |
It was fixed in |
Great, thanks Guillermo. Switched to master and http://github.com/dshaw/remoteconsole is working great. |
- Remove deprecated iOS 7.1 - Add Firefox and Microsoft Edge browsers - Add latest stable Node.js release
Bump dependencies, update package.json and travis settings
Streamie.org was crashing constantly with a message that in line 23 of websocket.js this.connection did not have a method of "setTimeout"
Because this was the production system I added a line
if(!this.connection.setTimeout) return;
This works around the server-crash issue for me.
I now get this constantly
3 Sep 14:31:07 - Initializing client with transport "websocket"
3 Sep 14:31:07 - WebSocket connection invalid
I suspect a faulty client is reconnecting all the time.
The text was updated successfully, but these errors were encountered: