Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Alkor San
    @alkorsan
    yes true; but I need to receive more than one message sometimes so read did t gave this flexibility
    Vitaly Shukela
    @vi
    Are you familiar with expect(1) program? It should be able to drive websocat too. Maybe it is a good choice when there are multiple line types and timeouts involved.
    Alkor San
    @alkorsan
    yes
    yes I m leaving it as my last solution
    Vitaly Shukela
    @vi
    Maybe websocat + bash combo is just not enough for the task. websocat + your_C_or_python_program or just your_python_program would be more fit for production.
    Alkor San
    @alkorsan
    because I found that websocat solved everything
    I don t think I need it now you made websocat a swissknife now
    but you already solved everything sir!
    it works super
    the new errors are not related to this problem at all
    Vitaly Shukela
    @vi
    OK. But if you need stability and resilience in corner cases, the exact details of websocat usage need to be reviewed.
    Please close the GitHub issues that you think are not relevant anymore.
    Alkor San
    @alkorsan
    ok
    Vitaly Shukela
    @vi
    Uploaded the 1.0.0 release files.
    Alkor San
    @alkorsan
    congratulation
    I tested wss and still have the same error!
    Vitaly Shukela
    @vi
    What about the pre-built executable?
    What about the mentioned cargo run command?
    Alkor San
    @alkorsan
    I m just attempting to test cargo run
    the pre-built exes gave the same error
    Vitaly Shukela
    @vi
    Reproduced the issue locally.
    Alkor San
    @alkorsan
    ok
    the same error with cargo run:
    websocat: Unknown address or overlay type of wss://echo.websocket.org
    error: process didn't exit successfully: binbadr\release\websocat.exe -v wss://echo.websocket.org
    (exit code: 1)
    Vitaly Shukela
    @vi
    Pushed to git and re-uploaded websocat_win32.exe and websocat_win64.exe to the release.
    Alkor San
    @alkorsan
    ok I will test
    now it works :)
    thank you
    both 32 / 64
    Alkor San
    @alkorsan
    building from source too works now for wss
    Vitaly Shukela
    @vi
    Shiny new option: --jsonrpc. It turns qwe 4,5,6 into {"jsonrpc":"2.0","id":1, "method":"qwe", "params":[4,5,6]} automatically.
    Alkor San
    @alkorsan
    fantastic , it works good in windows
    echo "qwe 4,5,6" | websocat.exe --jsonrpc  ws://echo.websocket.org/
    {"jsonrpc":"2.0","id":1, "method":"qwe", "params":[4,5,6]}
    thank you
    Vitaly Shukela
    @vi
    id increments automatically.
    Alkor San
    @alkorsan
    oh I didn t notice that. well done
    is it posible to remove the "jsonrpc":"2.0" part?
    because it is added without asking them to do , and if the server can t parse it then one have to remove it first before sending
    Vitaly Shukela
    @vi
    It's part of JSON RPC 2.0. What server fails when this is present?
    I checked that it works with Chromium remote debug mode.
    Alkor San
    @alkorsan
    sorry i thought it will not work with chromium server
    thank you very much
    Vitaly Shukela
    @vi
    If you find a server that really fails when this field is present (or, for example, requires "1.1" instead of "2.0"), give a notice and I make it overridable.
    Alkor San
    @alkorsan
    yes ok
    Raine Virta
    @raine
    please add installation instructions in the readme
    even if it's just "build from source like this"
    Raine Virta
    @raine
    okay, after doing the building from source part, I realized you can do cargo install websocat (I'm new to rust)
    Alkor San
    @alkorsan
    i m a user too like you and don t know rust too. the owner "Vitaly Shukela" explained to me to do this too if you want ssl
    cargo build --release --features=ssl
    --release makes the final exe smaller but it takes a litle bit more time to compile
    Vitaly Shukela
    @vi
    cargo install websocat should work even without manually downloading the source code.
    Added a step about finding the built executable in README.