vi / websocat

Command-line client for WebSockets, like netcat (or curl) for ws:// with advanced socat-like functions
MIT License
6.73k stars 259 forks source link

`broadcast:` problems on Windows #124

Open vi opened 3 years ago

vi commented 3 years ago

I am using websockat v1.8 (windows prebuilt version).

If I am using "broadcast:wss://****" very often websocat crushes.

I have 3 local clients connecting to tcp-l port (usually quickly). Sometime connection works, but mostly websockat crushes. Using -E flag does not have effect.

I am not posting this to github because their signup procedure with dice captcha is idiotic.

"websocat_win64.exe" --ping-interval 180 --text tcp-l:127.0.0.1:8091 broadcast:wss://************
websocat: Unfortunately, serving multiple clients without --exit-on-eof (-E) or with -U option is prone to socket leak i
n this websocat version
[WARN  websocat::ws_peer] unsync/oneshot: oneshot canceled
thread 'main' panicked at 'invalid key', /rustc/c7087fe00d2ba919df1d813c040a5d47e43b0fe7\src\libstd\macros.rs:13:23
stack backtrace:
   0:           0x4909b1 - <unknown>
   1:           0x45861b - <unknown>
   2:           0x48fa09 - <unknown>
   3:           0x48f3b3 - <unknown>
   4:           0x48e847 - <unknown>
   5:           0x45de20 - <unknown>
   6:           0x501cc5 - <unknown>
   7:           0x4e9c7e - <unknown>
   8:           0x503f24 - <unknown>
   9:           0x407663 - <unknown>
  10:           0x4052ed - <unknown>
  11:           0x411e10 - <unknown>
  12:           0x4138e7 - <unknown>
  13:           0x4a8b96 - <unknown>
  14:           0x41fa2e - <unknown>
  15:           0x4013c7 - <unknown>
  16:           0x4014fb - <unknown>
  17:         0x778c652d - <unknown>
  18:         0x779fc521 - <unknown>