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.
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.