On Thu, 9 Feb 2006, Shmulik Regev wrote:

> 4. The initial request issues a DNS query that is resolved to that unique
> fake IP and the result is cached. Obviously the request fails but this is
> not the issue.

But it is! Doesn't the whole connection fail? If so, the cached entry
should've been pruned, shouldn't it?

> 5. The application continue to run and but the curl based implementation
> (that uses persistent connections on a multi handle) never gets the true IP
> only the first one which is obviously invalid.

I don't see why the cached one would remain... I mean, unless there's
something more to this than what I previously explained.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html