Error serving client: WebSocket protocol error: Sending after closing is not allowed about wsbroad HOT 5 OPEN

I expect the error to be non-fatal. --exit-no-eof may abandon a connection without proper WebSocket close and I expect wsbroad to just continue handling other connected clients.

from wsbroad.

can websocat send message finished, and send close WebSocket to wsbroad as normal usage?

from wsbroad.

Just remove --exit-on-eof? It will send one message, receive one reply message and exit.

If you don't want to receive a reply, use -u (--unidirectional).

from wsbroad.

message sended:

client received message:

Error serving client tips also print in console.

from wsbroad.

Do you need to just inhibit those messages from wsbroad?

I see everything works more or less properly, aside from the annoying console messages.

I tried locally and do not see those unclean disconnection messages. Is there anything special between wsbroad and websocat instances? Is it on Linux?

To aid debugging, you can attach a traffic dump (pcap) of the experiments.

from wsbroad.