This repository was archived by the owner on Dec 18, 2018. It is now read-only.
This repository was archived by the owner on Dec 18, 2018. It is now read-only.
Don't send OPTIONS request if the user explicitly requests the WebSocket transport #1035
Description
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Give feedbackNo fields configured for issues without a type.
WebSocket transport does not need a connection id to work correctly because once it is connected it will stay connected. As a result we don't have to send the OPTIONS request. This will also lift the sessions stickiness requirement for WebSockets. Note: the user needs to make sure that the server supports WebSockets and that the WebSockets transport is enabled on the server (or use transport fallback)