Thanks, Daniel. Maybe this is a misunderstanding on my part, but I think (and my testing seems to confirm) that CURLOPT_CONNECT_ONLY will stop at the first connection to the first server encountered. If you have some other http redirector in front of the ultimate server hosting the websocket, or the websocket server returns 429 to indicate it's busy, try again later, the app must then handle all this work (I think ... I certainly could be wrong).
In my use cases, I'm generally asking libcurl to use HTTP to do redirection and traffic reduction things with libcurl, then after the "exciting bits" are done, I'd like to take ownership of the socket. On Wed, Jun 30, 2021 at 6:07 AM Daniel Stenberg <dan...@haxx.se> wrote: > > On Thu, 24 Jun 2021, Weston Schmidt via curl-library wrote: > > > This has been good feedback, thank you all. I'm going to work on writing up > > what has been covered into a proposal here: > > https://github.com/schmidtw/curl-websocket-proposal > > I created a "home" for the WebSockets brain-storming in curl's wiki: > > https://github.com/curl/curl/wiki/WebSockets > > -- > > / daniel.haxx.se > | Commercial curl support up to 24x7 is available! > | Private help, bug fixes, support, ports, new features > | https://www.wolfssl.com/contact/ ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
