You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that AWS's WebSocket client API misses messages that get sent immediately after connection roughly 8 out of 10 times.
I've tested this by opening a connection to wss://echo.websocket.org and waiting for a message, which sometimes comes and sometimes doesn't. Testing with an online WebSocket tester tool gets the message every time.
The code for the main program above is as follows:
For reference, here's what an online WebSocket test tool shows after connecting and disconnecting a few times:
Unfortunately, some APIs (e.g. Discord's Gateway API) rely on the server sending a message immediately after connecting, preventing these APIs from being used with AWS.
Also, in case it matters, I tested this from a freshly-built AWS from the master branch with SOCKET=openssl, on Debian Testing running under WSL2 (so kernel 5.15.167.4-microsoft-standard-WSL2).
The text was updated successfully, but these errors were encountered:
It seems that AWS's WebSocket client API misses messages that get sent immediately after connection roughly 8 out of 10 times.
I've tested this by opening a connection to wss://echo.websocket.org and waiting for a message, which sometimes comes and sometimes doesn't. Testing with an online WebSocket tester tool gets the message every time.
The code for the
main
program above is as follows:For reference, here's what an online WebSocket test tool shows after connecting and disconnecting a few times:
Unfortunately, some APIs (e.g. Discord's Gateway API) rely on the server sending a message immediately after connecting, preventing these APIs from being used with AWS.
Also, in case it matters, I tested this from a freshly-built AWS from the master branch with SOCKET=openssl, on Debian Testing running under WSL2 (so kernel 5.15.167.4-microsoft-standard-WSL2).
The text was updated successfully, but these errors were encountered: