Skip to content

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

Description

@millfort

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.

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    to triageWaiting to be triaged by a member of the team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions