Skip to content
This repository has been archived by the owner on May 2, 2023. It is now read-only.

Close Reason for token revocation is not returend #29

Open
eitan101 opened this issue May 22, 2017 · 3 comments
Open

Close Reason for token revocation is not returend #29

eitan101 opened this issue May 22, 2017 · 3 comments

Comments

@eitan101
Copy link
Contributor

agent.on('closed', reason => {
    // socket is now closed
})

Reason is 1006 also for token revocation instead of 4401.
Known issue. Should be fixed by the service.

@donmanguno
Copy link
Contributor

@miki2826 Is there anything we can do about this?

@miki2826
Copy link
Contributor

miki2826 commented Mar 1, 2018

@donmanguno unfortunately, this wasn't fixed in the service yet

@A142899
Copy link

A142899 commented Mar 28, 2022

Any updates on this?
And is there any way for me to tell when there's been a token revocation?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants