On Fri, 9 Oct 2020, Sean Miller via curl-library wrote:
(This might be a varation of this issue:
https://github.com/curl/curl/issues/5747 )
In response, libcurl appears to create a socket for DNS resolution without
asking for it via CURLOPT_OPENSOCKETFUNCTION.
That's correct, because it isn't a regular socket. It's a socketpair.
CURLMOPT_SOCKETFUNCTION should get told about it though. Doesn't it?
Is this behavior intentional? Is there a recommended way to either force
libcurl to ask for the socket, or else avoid telling me about it? Where did
I go wrong?
Yes and no. It is a socketpair used to signal when the resolve is complete. It
isn't a plain old socket so CURLOPT_OPENSOCKETFUNCTION cannot be used for it.
--
/ 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.haxx.se/mail/etiquette.html
