Daniel Egger
Daniel Egger
These are the last lines of output: ``` [INFO websocat::ws_server_peer] Upgraded [INFO websocat::broadcast_reuse_peer] Reusing [TRACE websocat::my_copy] poll [TRACE websocat::my_copy] poll [TRACE websocat::my_copy] poll [DEBUG websocat::ws_peer] drop WsWriteWrapper websocat: WebSocketError: WebSocket...
> Is it reproducible when using websocat ws://127.0.0.1:8090 as a client and interrupting it with Ctrl+C? Yes. > What platform is it on? Linux,Windows,Mac,Other? Mac
I haven't tried older versions, only 1.3.0. I also tried bumping all dependencies (except hyper which is API incompatible) but no change.
cargo installed it.
Same behaviour with `websocat_mac` downloaded from GitHub, though.
Same thing for v1.1.0. But I'm afraid I don't really have time to deeply analyse it right now.
`websocat -t -E tcp-l:127.0.0.1:8090 -` -> same problem
No idea, I'm writing my own WS implementation for a commercial product and I'm trying to use websocat as counterpart. It seemed as if ping was implemented already so that's...
If no `--protocol` is specified but the client contains the header my idea would be to: * Return the same `Sec-WebSocket-Protocol` header if exactly one protocol is specified * Return...