Re :Re: Need more information on handling ares with libcurl
Date: 2 Nov 2008 12:45:55 -0000
On Fri, 31 Oct 2008 23:23:11 +0100 (CET) libcurl development wrote On Thu, 30 Oct 2008, vishnu sankar wrote: > My development and testing environament are linux.I configured my dns > resolver to a network which is not reachable.configured CURLOPT_NOSIGNAL and > CURLOPT_TIMEOUT (2 secs ) options for easy handle.My multiperform > returned asynchronously. I got the file descriptors as my active running > handles is 1 and registered them for data.At this time i am not recieving > any data for my registered file descriptors nor a time out response is > initiated from libcurl With no signals and without c-ares, libcurl can't abort the resolve at the desired time-out so you need to wait until the regular name resolve function call returns.>>>>> I have actually compiled my libcurl with c-ares.But i configured my resolver address(in resolv.conf) as a unreachable network > .I dont expect any data because the reso!
lver is not reachable and cant > resolve my domain name . But i am expecting a time out response from > libcurl which is not happening. Timeout is happening fine when i use libcurl > without c-ares support I've never seen anyone experience c-ares builds to not deal with timeouts properly before. Are you using the latest libcurl and c-ares? If so, can you provide us with the source for an app that repeats this problem?>>>>I am using latest curl and ares builds .The timeout is working fine if the resolver network is reachable (configured in resolv.conf).In this case we recieve some data from resovler server and multi perform in again called which calls the resolver functctions if the timeout has occured or not.Is time out handled in case the resolver network is unreachable There is no response from the resolver as the resolver network is not reachable..Due to which the file descriptors for which i registered for response are!
not receving any response and multi perform function is not called .Since multi perform function is not called , the timeout is not handled. The only change i have done is to reproduce this is i am configuring my resolver to an u nreachable network. For a resolver which is reachable, timeouts are working fine. -- / daniel.haxx.se
Received on 2008-11-02