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
If I use the web socket chat example verbatim.
and then open a web-socket using curl. curl --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ==" --header "Sec-WebSocket-Version: 13" http://127.0.0.1:3030/chat
The server becomes completely unresponsive, and the logs spam with DEBUG warp::filters::ws > websocket poll error: Trying to work with closed connection
indefinitely. I'm not exactly sure why this occurs. Something with curl opening and closing the connection too quickly perhaps?
The text was updated successfully, but these errors were encountered:
@asonix Sorry I didn't think the fix was worth responding, as it's just an example.
The problem is here.
If you simply change the continue to a break, the issue is eliminated.
I'm not sure if there could be errors that should be ignored, instead of closing, however.
If I use the web socket chat example verbatim.
and then open a web-socket using curl.
curl --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Sec-WebSocket-Key: SGVsbG8sIHdvcmxkIQ==" --header "Sec-WebSocket-Version: 13" http://127.0.0.1:3030/chat
The server becomes completely unresponsive, and the logs spam with
DEBUG warp::filters::ws > websocket poll error: Trying to work with closed connection
indefinitely. I'm not exactly sure why this occurs. Something with curl opening and closing the connection too quickly perhaps?
The text was updated successfully, but these errors were encountered: