Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Should we CURL_SOCKET_TIMEOUT after curl_multi_add_handle?

From: Jeff Mears via curl-library <curl-library_at_cool.haxx.se>
Date: Wed, 14 Oct 2020 18:26:50 +0000

We use libcurl's "multi" interface on a server to dispatch HTTPS requests when the server code decides it needs to. We create an easy handle, then call curl_multi_add_handle to trigger the download.

According to this web page, though:

https://ec.haxx.se/libcurl/libcurl-drive/libcurl-drive-multi-socket

we're supposed to immediately call curl_multi_socket_action with CURL_SOCKET_TIMEOUT after starting a request.

We ended up with several questions about this:

 * Is it actually necessary to do this?

 * What would happen if we didn't?

 * How does this interact with an existing timeout that curl set before the handle was added? Do we continue to fire that later, or do we cancel it?


Thank you!

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-10-14