Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Raine Virta
    @raine
    it's fairly common for project's to have "Installation" section in the README at close to top with instructions on how to install
    Alkor San
    @alkorsan
    me too i vote to add this
    Vitaly Shukela
    @vi
    Should it be something like "add this to $PATH or use cargo install" or something more elaborate?
    Alkor San
    @alkorsan
    when we install rust it adds automatically the PATH, i think adding the commands to build is suficient + a link to download rust
    something like this maybe:
    install it and run:
    git clone https://github.com/vi/websocat
    cd websocat
    cargo build --release --features=ssl
    this is how they do in other projects like in go
    Raine Virta
    @raine
    # Installation
    
    1. [Install rust](https://www.rust-lang.org/en-US/install.html) if necessary
    2. `cargo install websocat`
    This would have saved 5 minutes for me
    Vitaly Shukela
    @vi
    It may be a bit misleading, as it downloads a separate copy of websocat source code, not uses the one you are running cargo install from.
    It should also cover installing pre-built binaries distributed using Github Releases.
    Alkor San
    @alkorsan
    yes
    Raine Virta
    @raine
    How does one add headers to this command websocat 'ws://localhost:8003/socket.io/?EIO=3&transport=websocket'?
    Trying to add -H Cookie:foo before the url but it's saying websocat: No URL specified
    Presumably the "simple mode" doesn't work if you add headers
    Vitaly Shukela
    @vi
    Strange.
    Try specifying the option after URL, not before.
    It assumes the URL is a second header.
    Raine Virta
    @raine
    Hey, that works
    Vitaly Shukela
    @vi
    It is to be fixed in next release.
    Raine Virta
    @raine
    Thank you
    Vitaly Shukela
    @vi
    Another way to specify it is websocat -H=Cookie:foo ws://..., with the equal sign.
    Vitaly Shukela
    @vi
    Added installation section to the README. Is it OK?
    Vitaly Shukela
    @vi
    Added SSL listener and SOCKS5 proxy support.
    Raine Virta
    @raine
    @vi much better
    (wrt. installation section)
    although I would place the section above Usage
    one of the most important bits of information user will be looking for on that page
    Vitaly Shukela
    @vi
    Done.
    Vitaly Shukela
    @vi
    Cooking a new release with -k (--insecure) option to force connecting to development wss://. It also should be buildable with newer OpenSSL.
    Vitaly Shukela
    @vi
    Websocat 1.2.0 now in Homebrew.
    Vitaly Shukela
    @vi
    Websocat in master now uses tokio instead of tokio-core. But still hyper 0.10 instead of 0.12 unfortunately.
    dsboo
    @dsboo
    hi:) thanks to websocket(your program). i want to send binary msg using this tool in client mode. but i can't find how to send binary msg from file or cli. could you give me a example?
    Vitaly Shukela
    @vi
    dsboo, cat myfile | websocat -b ws://destination/ or websocat -b readfile:myfile ws://destination ?
    If file is big, it would be split in mutliple WebSocket messages. Use -B option to override maximum message size.
    dsboo
    @dsboo
    thanks!
    is it impossible cli interaction?
    Vitaly Shukela
    @vi
    Do you mean interactively sending text messages, then send one-off message from file, then continue interactively typing text WebSocket messages?
    Kevin Elliott
    @kevinelliott
    Hello, I'm trying to use websocat to capture a stream at http://websdr.ewi.utwente.nl:8901/?tune=3715usb which has an embedded websocket at ws://websdr.ewi.utwente.nl:8901/~~stream?v=11 ... any thoughts?
    Vitaly Shukela
    @vi
    @kevinelliott You need to specify origin: websocat -b --origin http://websdr.ewi.utwente.nl:8901 ws://websdr.ewi.utwente.nl:8901/~~stream?v=11
    Kevin Elliott
    @kevinelliott
    Thanks, that worked. Looks like the data needs to get converted to audio somehow
    Vitaly Shukela
    @vi
    kevinelliott, If binary websocket message boundaries are significant then using websocat to decode that to audio may be problematic.
    David Cole
    @hadavarbarak
    We are trying to start a docker container with two listen proxy between tcp and ws. But when we connect to either opened port we get an immediate connection reset. When we do the same with the natively installed version of websocat it works fine. Has anyone else run into this?