SignalK / signalk-server-java

DEPRECATED - see https://github.com/SignalK/signalk-java
Apache License 2.0
6 stars 9 forks source link

wscat does not connect sucessfully #6

Closed rob42 closed 9 years ago

rob42 commented 9 years ago

If a client makes a ws connecction directly to the websocket port the sessionid and transport type are not set. This results in the reply being dropped in the output route as there is no transport type to direct the routing. Normally the sessionid and transport type are set on the initial browser connection (http) but this does not happen when wscat connects directly. Also affects instrumentpanel and possibly others.

rob42 commented 9 years ago

Changes made to ensure that sessionid and transport type are always set.