-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not connecting/reconnecting issues #2
Comments
Authorized actually means SSL authorization. |
yup, anything that would give me control over the retry connection or status of it would be perfect. |
added a pull request to fix this |
Merged. |
pushed to npm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hi
when i m using a wrong token i get into a re-connection loop stating that connection is authorized. Is there an event that we could use for when it fails and disable the loop maybe, or handle it in a more straightforward manner?
Cheers
The text was updated successfully, but these errors were encountered: