On gio, lug 11, 2013 at 03:37:41 -0700, Ludovico Cavedon wrote: > Hi, > Bug #605558 [1] is what caused libcurl to be compiled without c-ares support. > > Is the problem still there? > > [...] > > This makes me think the problem has been solved wither in curl or c-ares.
Yep, it was fixed in libcurl some time ago.
> It would be useful to have libcurl compiled with c-ares, because of [2].
Unfortunately it's not that simple. The c-ares resolver lacks somewhat important
features compared with the libc resolver, particularly the NSS libc thing (which
is what allows people to enable e.g. mDNS system-wide).
After a quick look at the libcurl code, it seems that enabling the threaded
resolver instead, would fix the problem you linked to, since it doesn't use
alarm just like the c-ares version, and would also bring async resolving. But
it'd probably have some bad effect on performance... so yeah, I'll see what I
can do but I can't promise anything.
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
