6 commits

Author	SHA1	Message	Date
ayeteadoe	58be9e6400	RequestServer: Enable in Windows CI	2025-08-23 16:04:36 -06:00
Abhinav	0205480051	LibWeb: Process closure of socket for WebSockets	2025-08-18 09:35:47 -06:00
Luke Wilde	9c5dff5be0	RequestServer+LibWebSocket: Drain underlying socket and resulting frames ... `curl_easy_recv` must be called in a loop until it returns EAGAIN, because it may cache data, but only activate the read notifier once. Additionally, the data received can contain multiple WebSocket frames and only activate the notifier once, so we have to keep reading frames until there isn't enough data. We also have to do this immediately after connecting a WebSocket, since the server may immediately send data when the WebSocket opens and before we create the read notifier. This makes Discord login faster and more reliable, and makes Discord activities start loading.	2025-07-22 13:55:45 +02:00
Mohamed amine Bounya	b77643a2e8	RequestServer: Don't assert for socket fd not being CURL_SOCKET_BAD ... The assertion in `WebSocketImplCurl::did_connect()` keeps failing for multiple websockets when loading `https://www.speedtest.net/` since commit 14ebcd4. This fixes that by checking and returning false if something went wrong and letting the caller function handle it.	2025-04-30 18:20:26 -06:00
Andrew Kaster	06faa7b160	LibWebSocket+RequestServer: Resolve WebSocket hosts using our resolver	2025-02-20 15:04:50 -07:00
Andrew Kaster	71942d53eb	LibWebSocket+RequestServer: Add a WebSocketImpl using libcurl ... This implementation can be better improved in the future by ripping out a lot of the manual logic in LibWebSocket and rely on libcurl to parse our message payloads. But for now, this uses the 'raw mode' of curl websockets in connect-only mode to allow for somewhat seamless integration into our event loop.	2025-02-20 15:04:50 -07:00