-
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
Multiplexing connection and client disconnect #601
Comments
Moved to socket.io-client. |
This was referenced Jan 8, 2021
darrachequesne
added a commit
that referenced
this issue
Jul 8, 2024
In order to catch the following errors: ``` events.js:288 throw er; // Unhandled 'error' event ^ Error: write EPIPE at afterWriteDispatched (internal/stream_base_commons.js:154:25) at writeGeneric (internal/stream_base_commons.js:145:3) at Socket._writeGeneric (net.js:780:11) at Socket._write (net.js:792:8) at doWrite (_stream_writable.js:441:12) at writeOrBuffer (_stream_writable.js:425:5) at Socket.Writable.write (_stream_writable.js:316:11) at abortConnection (<myproject>/node_modules/engine.io/lib/server.js:506:12) at <myproject>/node_modules/engine.io/lib/server.js:353:7 at Server.verify (<myproject>/node_modules/engine.io/lib/server.js:158:14) at Server.handleUpgrade (<myproject>/node_modules/engine.io/lib/server.js:351:8) ``` Closes socketio/engine.io#596, socketio/engine.io#598
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm writing python server implementation for 0.8x socket.io and stumbled upon a problem.
If I have two namespaced connections over one transport connection, I see following in my logs:
1::/chat
1::/ping
Which is correct.
Then, on client side I'm doing chat.close() which sends following packet:
0::/chat
But anytime I want to reconnect chat socket by doing:
chat = io.connect('http://localhost:8001/chat')
It is not sending anything to the server - it does not attempt to reestablish virtual connection.
When I'm doing chat.send('blabla'), I'm seeing message being sent to the server:
3::/chat:blabla
Obviously, server does not like it and rejects.
The text was updated successfully, but these errors were encountered: