Results 825 comments of Vitaly Shukela

Indeed, `libatomic.so.1` crept in for some reason. Unfortunately, there are no _real_ tests for Websocat, so each release may introduce regressions. Now investigating how to restore staticness.

Dynamicness originates from built-in OpenSSL. Here is a version of Websocat without TLS support, if this is enough for you. [websocat_nossl.arm-unknown-linux-musleabi.zip](https://github.com/vi/websocat/files/13531495/websocat_nossl.arm-unknown-linux-musleabi.zip)

Here is another attempt to build for `arm-unknown-linux-musleabi`, now with OpenSSL, but it does not work for me if I try to connect to `wss://` (segmentation faullt), unlike version 11....

Here is a Websocat executable for Raspberry Pi 2 (using system openssl): [websocat-rpi2.zip](https://github.com/vi/websocat/files/15497258/websocat-rpi2.zip) It is enough?

At least printing of `Location:` in a more user-friendly way can be an option for quick implementation. Proper redirects may be more of Websocat3 material.

Probably `libssl1.0.2`. Here is a version with a static openssl that is hopefully more portable: [websocat-armhf.zip](https://github.com/user-attachments/files/15506452/websocat-armhf.zip) And here is one without TLS support: [websocat-armhf-nossl.zip](https://github.com/user-attachments/files/15506505/websocat-armhf-nossl.zip) They are not static, but built...

In Websocat 1.12: ``` $ websocat ws://127.0.0.1:7780/ websocat: WebSocketError: WebSocketError: Redirected (302 Found) to http://example.com/ websocat: error running ```

Are you sure it works as desired after removing `--binary`? `--base64` is probably meaningless without either `--binary` or `--binary-prefix`. Or have you decoded the file manually, outside of Websocat? Small...

You can control chunking by using large buffer size, `line2msg:` overlay and `--base64` option. Each line of input file will be converted to a WebSocket message.

`-v` prints messages. `-v -v` increases verbosity. Other features affecting logging are `--stdout-announce-listening-ports` option and `log:` overlay.