On Tue, 10 Jun 2008, Christopher Palow wrote:

> So when trying to do a POST (I don¹t think it matters POST or GET) with the
> multi interface with libcurl from cvs and c-ares (also from cvs) I noticed
> the following behavior. Cares will do the blocking I/O to check /etc/hosts
> (maybe we can expose the struct ares_options.lookups = "b" as a curl multi
> option)

That's an idea, yes...

> Libcurl will provide back via the socket_change_callback that the app should
> listen for the DNS lookup¹s response. However, once the DNS lookup succeeds
> it won¹t tell the client app to stop looking for the DNS lookup¹s response
> like the way libcurl does for other types of connections. I feel this is a
> bug and will dig into the code a little to provide a fix. Thoughts?

If that is indeed what happens then it certainly is a bug. Latest libcurl and
c-ares running?

(libcurl should actually be fixed to use the socket callback functionality of
c-ares...)

-- 
  / daniel.haxx.se