Hi folks,
I went ahead and created a patch to provide a new libcurl CB, that will be
called just before a new resolver is called, and the resolver data (channel in
case of cares) is passed. This solves the problem perfectly for my use case.
Initially I thought about just adding a new easy_geti
Hello Daniel,
I feel it would be useful in some other cases - for example dealing with
multi-vrf sockets, currently you can bind the libcurl socket to any vrf you
want, but no way to do that with the underlying c-ares.
Wouldn't be enough to provide access to the c-ares channel (which is in
cur
On Tue, 13 Feb 2018, Francisco Sedano Crippa (fsedanoc) wrote:
Ideally I’d like to setup a callback with
ares_set_socket_configure_callback(), but in order to do so, I need access
to internal libcurl c-ares channel, which is embedded in the Curl_easy
structure.
Is there any way to access suc
Hello folks,
In our environment, we need to setup some socket options before sockets can be
used, and we need to use curl + c-ares.
Ideally I’d like to setup a callback with ares_set_socket_configure_callback(),
but in order to do so, I need access to internal libcurl c-ares channel, which
is
