javascript clients close the connection on permission error #265
Assignees
Comments
aricart
added a commit
that referenced
this issue
Feb 18, 2022
…mission errors, this changes the behaviour to match other client implementations. Note that in some cases (like pub/req permissions) the only way to know that there was a permission error is via the status. On subscriptions, if callback, the `err` argument will provide the same. [FIX] on iterators, if a permission error triggered, the connection was closed, but the promise from the subscription backing it, remained pending. Fixes #265
Merged
aricart
added a commit
that referenced
this issue
Feb 20, 2022
…mission errors, this changes the behaviour to match other client implementations. Note that in some cases (like pub/req permissions) the only way to know that there was a permission error is via the status. On subscriptions, if callback, the `err` argument will provide the same. (#267) [FIX] on iterators, if a permission error triggered, the connection was closed, but the promise from the subscription backing it, remained pending. Fixes #265
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The JavaScript client since 2.0 deviates from standard practice of allowing clients to keep connected when pub/sub pub/sub permissions are raised.
The text was updated successfully, but these errors were encountered: