Question

WebSocket debug

Answer 1

MUST be 0 unless an extension is negotiated that defines meanings
for non-zero values. If a nonzero value is received and none of
the negotiated extensions defines the meaning of such a nonzero
value, the receiving endpoint MUST _Fail the WebSocket
Connection_.

Comments

Hello, send log file to your email.

---

Thank you for the log file. It helped a lot to diagnose the issue.

The issue is caused by using the permessage-deflate extension (defined by RFC 7692), which is currently unsupported by Rebex WebSocket solution.

You sent this HTTP request header:
 Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits

which enabled the permessage-deflate extension at the server (but not at the client). This extension uses reserved RSV1 flag to specify that compression is in use.


To solve the issue, please do set permessage-deflate extension. Or even better, do not set the Sec-WebSocket-Extensions header because the client will not be able to handle the specified extensions anyway.


However, we are planning to add support for permessage-deflate extension in a future.