Michal

Hi @nicolasff, there is a test page for crash: ``` function testStreamRead() { var xrSocket = new WebSocket("wss://develserver/webdis/.json"); xrSocket.onmessage = function(messageEvent) { console.log("JSON XREAD received:", messageEvent.data); xrSocket.send(JSON.stringify(["XREAD", "BLOCK", 15000, "COUNT",...

I'm afraid, that there are some next problematic points. :-( But for your last two mentioned: This bug with restarted Redis is related to incorrect reaction on Redis callback with...

To discuss how to deal with fair closing from the perspective of HTTP (WS) and Redis side, I'm thinking that a possible solution using a structure like this: ```ags struct...

Thank you for accepting and properly refining my crazy idea :-) A slightly different solution will probably be needed for the websocket connection, as there may be a number of...

I looked at this issue again: > For example, even with your patch if you: > > 1. Load the test page and have the WS client connect > >...

Regarding masking - similar to the requirement for the CLOSE frame, the RFC above states that the client must send all payloads with masking. I went through the RFC one...

Maybe a bit better version of a patch for the `ws_peek_data(...)` function: ```diff --- websocket.c.orig 2022-01-10 12:50:20.331031836 +0100 +++ websocket.c 2022-01-15 13:08:03.661929542 +0100 @@ -234,6 +234,7 @@ static void ws_log_cmd(struct...