From 255dc45dc986a193a1def2f76a1b0bea2a5b7dd5 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Mon, 27 Apr 2009 12:23:53 +0000 Subject: [PATCH] the windows threaded resolver isn't foolproof enough --- docs/KNOWN_BUGS | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 8e3e209ce..edc614792 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -3,6 +3,11 @@ join in and help us correct one or more of these! Also be sure to check the changelog of the current development status, as one or more of these problems may have been fixed since this was written! +64. The threaded resolver used in libcurl on Windows has some kind of race + problem when multiple simultanoes resolves are done, like with the multi + interface transferring many files in parallell: + http://curl.haxx.se/mail/lib-2009-04/0028.html + 63. When CURLOPT_CONNECT_ONLY is used, the handle cannot reliably be re-used for any further requests or transfers. The work-around is then to close that handle with curl_easy_cleanup() and create a new. Some more details: