Skip to content

WebSocket: Subprotocol incorrectly treated as mandatory #369

@ting-fx

Description

@ting-fx

Describe the bug
The current WebSocket implementation incorrectly requires a subprotocol (Sec-WebSocket-Protocol) during the opening handshake. If no subprotocol is specified, the WebSocket connection fails. According to RFC 6455, subprotocol negotiation is optional.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions