Proper Errorcode reporting

[yassinebenarbia]

Story

I was implement a WS server and tried using websocat to debug it but ran into this error message:

websocat: WebSocketError: I/O failure
websocat: error running

After spending hours of debugging, I tried using other clients (claws ) and it turns out that it's an abnormal connection closing (error code 1006) which what websocat failed to convey.

Suggestion

Implement proper error message handling with informative error messages, or at least include a status codes (from RFC) in the so people can lookup the problem.

For Reference:

https://www.rfc-editor.org/rfc/rfc6455.html

[vi]

Have you tried using websocat4 --log-traffic or a Websocat1 equivalent to see the frames? Maybe it would have led to the solution quicker, though you would needed to decode the two bytes of a close code manually from hex or ascii.

Mentioning content of a close frame and decoding the code in a diagnostic message is indeed a good idea, though I'm not sure if it will be in Websocat1.

Along the way there should be options to specify close codes and payloads of emitted payloads for testing.

---

I'm not sure it is needed for a "proper RFC implementation" - ignoring content of close frames does not seem to go against the RFC.

[yassinebenarbia]

I've tried RUST_LOG=debug but didn't get much useful information from it, and I'm not so sure that I follow about websocat4 --log-traffic

[vi]

websocat4 means using websocat4 branch or an alpha release.