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
Many browsers / client side implementations of the WebSocket protocol send a frame with a null byte just before disconnecting, in that case, the user of the library should not receive an OnMessage event.
The text was updated successfully, but these errors were encountered:
Also, the OnMessage event should not be invoked if the message is comprised only of a unicode control character, because it seems like some browsers like to not follow the WebSocket specification and send things like an ETX unicode character in a data frame when the socket closes
Many browsers / client side implementations of the WebSocket protocol send a frame with a null byte just before disconnecting, in that case, the user of the library should not receive an OnMessage event.
The text was updated successfully, but these errors were encountered: