From dfe1884c2529d728750d0824f73055627673cd72 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 22 Jun 2006 21:36:53 +0000 Subject: Peter Silva introduced CURLOPT_MAX_SEND_SPEED_LARGE and CURLOPT_MAX_RECV_SPEED_LARGE that limit tha maximum rate libcurl is allowed to send or receive data. This kind of adds the the command line tool's option --limit-rate to the library. The rate limiting logic in the curl app is now removed and is instead provided by libcurl itself. Transfer rate limiting will now also work for -d and -F, which it didn't before. --- docs/KNOWN_BUGS | 4 ---- 1 file changed, 4 deletions(-) (limited to 'docs/KNOWN_BUGS') diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 928ae49ad..38c657f03 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -103,10 +103,6 @@ may have been fixed since this was written! http://curl.haxx.se/bug/view.cgi?id=1004841. How? http://curl.haxx.se/mail/lib-2004-08/0182.html -9. --limit-rate using -d or -F does not work. This is because the limit logic - is provided by the curl app in its read/write callbacks, and when doing - -d/-F the callbacks aren't used! http://curl.haxx.se/bug/view.cgi?id=921395 - 8. Doing resumed upload over HTTP does not work with '-C -', because curl doesn't do a HEAD first to get the initial size. This needs to be done manually for HTTP PUT resume to work, and then '-C [index]'. -- cgit v1.2.3