On Wed, 30 Jun 2021, Weston Schmidt wrote:
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).
No, that's a correct understanding. CURLOPT_CONNECT_ONLY, as the name implies only does the connect part and then stops.
The similarity it would share with websockets-in-curl is how it doesn't actually do any transfer, but will just do a controlled set of setting up protocol things and then return.
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.
And that's not a feature we have in current libcurl... but I don't think it would be too complicated to add if we end up deciding that's what we need.
-- / 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
