Skip to content
This repository was archived by the owner on Apr 13, 2020. It is now read-only.

wscat does not connect sucessfully #6

Closed
rob42 opened this issue Apr 9, 2015 · 1 comment
Closed

wscat does not connect sucessfully #6

rob42 opened this issue Apr 9, 2015 · 1 comment

Comments

@rob42
Copy link
Contributor

rob42 commented Apr 9, 2015

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
Copy link
Contributor Author

rob42 commented Apr 9, 2015

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

@rob42 rob42 closed this as completed Apr 9, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rob42