Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Inconsistent behavior of close packet processing in websocket and polling transports #5286

Open
millfort opened this issue Jan 30, 2025 · 0 comments
Open

Inconsistent behavior of close packet processing in websocket and polling transports #5286

millfort opened this issue Jan 30, 2025 · 0 comments
Labels
to triage Waiting to be triaged by a member of the team

Comments

@millfort
Copy link

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.
@millfort millfort added the to triage Waiting to be triaged by a member of the team label Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
to triage Waiting to be triaged by a member of the team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@millfort