From 0682d25da5036d2b35e890808247e9203d28fcc4 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Tue, 2 Jan 2007 22:34:56 +0000 Subject: - Victor Snezhko helped us fix bug report #1603712 (http://curl.haxx.se/bug/view.cgi?id=1603712) (known bug #36) --limit-rate (CURLOPT_MAX_SEND_SPEED_LARGE and CURLOPT_MAX_RECV_SPEED_LARGE) are broken on Windows (since 7.16.0, but that's when they were introduced as previous to that the limiting logic was made in the application only and not in the library). It was actually also broken on select()-based systems (as apposed to poll()) but we haven't had any such reports. We now use select(), Sleep() or delay() properly to sleep a while without waiting for anything input or output when the rate limiting is activated with the easy interface. --- docs/KNOWN_BUGS | 7 ------- 1 file changed, 7 deletions(-) (limited to 'docs') diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 3c25d9f79..2ccabb82f 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -10,13 +10,6 @@ may have been fixed since this was written! when doing the different passes in the NTLM negotiation and thus fail to negotiate (in seemingly mysterious ways). -36. --limit-rate (CURLOPT_MAX_SEND_SPEED_LARGE and - CURLOPT_MAX_RECV_SPEED_LARGE) are broken on Windows (since 7.16.0, but - that's when they were introduced as previous to that the limiting logic was - made in the application only and not in the library). This problem is easily - repeated and it takes a Windows person to fire up his/hers debugger in order - to fix. http://curl.haxx.se/bug/view.cgi?id=1603712 - 35. Both SOCKS5 and SOCKS4 proxy connections are done blocking, which is very bad when used with the multi interface. -- cgit v1.2.3