Lines Matching defs:timeout
115 This is intended to equal the c-ares default timeout. cURL always uses that
116 default value. Unfortunately, c-ares doesn't expose its default timeout in
183 options.timeout = CARES_TIMEOUT_PER_ATTEMPT;
188 if c ares < 1.20.0: curl set timeout to CARES_TIMEOUT_PER_ATTEMPT (2s)
190 if c-ares >= 1.20.0 it already has the timeout to 2s, curl does not need
191 to set the timeout value;
193 if c-ares >= 1.24.0, user can set the timeout via /etc/resolv.conf to
194 overwrite c-ares' timeout.
295 struct timeval *timeout;
303 timeout = ares_timeout((ares_channel)data->state.async.resolver, &maxtime,
305 milli = (long)curlx_tvtoms(timeout);
317 * 2) wait for the timeout period to check for action on ares' sockets.
362 above, as otherwise the ares name resolve won't timeout! */
453 timediff_t timeout;
459 timeout = Curl_timeleft(data, &now, TRUE);
460 if(timeout < 0) {
465 if(!timeout)
466 timeout = CURL_TIMEOUT_RESOLVE * 1000; /* default name resolve timeout */
475 itimeout = (timeout > INT_MAX) ? INT_MAX : (int)timeout;
477 itimeout = (int)timeout;
485 /* use the timeout period ares returned to us above if less than one
506 timeout -= 1; /* always deduct at least 1 */
507 else if(timediff > timeout)
508 timeout = -1;
510 timeout -= timediff;
513 if(timeout < 0)
623 quickly, but the other could always fail or timeout (when we're
635 addresses, or "no such domain"), we start a timeout for the remaining
648 c-ares query timeout. That is enough time for a typical parallel
652 c-ares timeout (5 seconds) plus the round trip time for the successful
656 timeout to prevent it. After all, we don't even know where in the