Searched refs:resolver (Results 26 – 35 of 35) sorted by relevance
12
133 - name: openssl libssh2 sync-resolver valgrind136 configure: --with-openssl --enable-debug --disable-threaded-resolver --with-libssh2212 …configure: --enable-debug --disable-shared --disable-threaded-resolver --with-libssh --with-openssl
197 … '!19 !1233', config: '--enable-debug --disable-threaded-resolver --disable-proxy',…198 … 'skiprun' , config: '--enable-debug --disable-threaded-resolver', name: 'default'…201 … 'skiprun' , config: '--enable-debug --disable-threaded-resolver --disable-curldeb…
178 - Name resolves unless the c-ares or threaded-resolver backends are used
922 Data pointer to pass to resolver start callback. See
745 data->state.async.resolver, in Curl_resolv()
610 void *resolver; /* resolver state, if it is used in the URL state - member
298 Curl_resolver_cleanup(data->state.async.resolver); in Curl_close()520 result = Curl_resolver_init(data, &data->state.async.resolver); in Curl_open()551 Curl_resolver_cleanup(data->state.async.resolver); in Curl_open()
441 Use getaddrinfo_a() to provide an asynch name resolver backend to libcurl470 - Name resolves on non-Windows unless c-ares or the threaded resolver is used.472 - The threaded resolver may block on cleanup:494 name when the DNS resolver can get flooded.
1258 change name resolver function you must rebuild libcurl and tell it to use a1261 - The non-IPv6 resolver that can use one of four different hostname resolve1269 - The IPv6-resolver that uses getaddrinfo()1271 - The c-ares based name resolver that uses the c-ares library for resolves.1274 - The threaded resolver (default option on Windows). It uses:
160 curl_res_msg="default (--enable-ares / --enable-threaded-resolver)"4179 AC_MSG_CHECKING([whether to use POSIX threads for threaded resolver])4182 [Enable POSIX threads (default for threaded resolver)])4228 dnl turn off pthreads if no threaded resolver4295 dnl threaded resolver check4306 AC_MSG_ERROR([Threaded resolver enabled but no thread library found])5420 resolver: ${curl_res_msg}
Completed in 59 milliseconds
