socket.io
socket.io copied to clipboard
Inconsistent behavior of close packet processing in websocket and polling transports
Describe the bug In the engine.io WebSocket transport, when a close packet is received, it is sent to the top in onPacket and the connection continues functioning as if nothing happened. In contrast, the polling transport closes the client and sends the close event to the top in onClose.
To Reproduce
Engine.IO server and client version: 72d61da Send close packet from server to client.
Expected behavior All transports should handle data processing consistently.