|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
We currently set the websocket subprotocol to be used for raw websocket in SockJS, but this header is not set when websockets are used in the SockJS protocol. As far as I know there is no way to specify the subprotocol when using SockJS, though I'll double check this. So specifying this for SockJS websockets in addition to the raw websockets transport, would fail the connection as the server will have responded with a subprotocol not requested by the client.