From: Daniel Stenberg Date: Wed, 23 Oct 2013 21:14:17 +0000 (+0200) Subject: CURLOPT_RESOLVE: mention they don't time-out X-Git-Tag: curl-7_34_0~203 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=947d431d5043b74e6a3b24f2295807055a140cff;p=thirdparty%2Fcurl.git CURLOPT_RESOLVE: mention they don't time-out Clarify in the documentation that DNS entries added with CURLOPT_RESOLVE won't time-out. Bug: http://curl.haxx.se/mail/lib-2013-10/0062.html Reported-by: Romulo Ceccon --- diff --git a/docs/libcurl/curl_easy_setopt.3 b/docs/libcurl/curl_easy_setopt.3 index b9d834b93a..f58c8fbfe1 100644 --- a/docs/libcurl/curl_easy_setopt.3 +++ b/docs/libcurl/curl_easy_setopt.3 @@ -2293,7 +2293,9 @@ ADDRESS can of course be either IPv4 or IPv6 style addressing. This option effectively pre-populates the DNS cache with entries for the host+port pair so redirects and everything that operations against the -HOST+PORT will instead use your provided ADDRESS. +HOST+PORT will instead use your provided ADDRESS. Addresses to set with +\fICURL_RESOLVE\fP will not time-out from the DNS cache like ordindary +entries. You can remove names from the DNS cache again, to stop providing these fake resolves, by including a string in the linked list that uses the format