fix(websocket): can connect now#349
Merged
Merged
Conversation
Closed
tisba
approved these changes
May 19, 2019
Collaborator
|
-duh- stupid thing here. Shows a bit how few actually use websockets with tsung. That issue has been around for a LONG time :-/ |
Collaborator
|
Thanks you for your contribution! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Okay I'm coming from #132 finally had the time.
With this change the websocket error mentioned is gone.
Didn't really do a real test scenario but from MongooseIM logs I can see traffic is coming in hot now 😃