You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the ws socket gets closed by peer, a closeResponse object is created but never used.
As the peer also is able to specify a close status + reason if would be nice to fetch these as well.
Today an exception is thrown with the message "Connection closed by the server", making it hard to take action as the reason for closure isn't known. My proposal is to throw a custom exception, including the close status, reason and the closeResponse message.
The text was updated successfully, but these errors were encountered:
When the ws socket gets closed by peer, a closeResponse object is created but never used.
As the peer also is able to specify a close status + reason if would be nice to fetch these as well.
Today an exception is thrown with the message "Connection closed by the server", making it hard to take action as the reason for closure isn't known. My proposal is to throw a custom exception, including the close status, reason and the closeResponse message.
The text was updated successfully, but these errors were encountered: