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
I did some more investigation and it seems somehow the browser sends an inappropriate message before sending the PONG. it might be related the proxy configuration in my system.
I was trying to send periodic ping messages from my server to a web client and it fails at the very first ping with the following error:
failed to ping: WebSocket closed: received header with unexpected rsv bits set: true:false:false
It seems the library does not allow the RSV1 bit for control messages here.
However both ping and pong might have payload accoring to the RFC:
and
So I assume compression should make sense for them too. I tried it with the latest dev version, with multiple browsers and the issues persisted.
The text was updated successfully, but these errors were encountered: