Skip to content
  1. Jun 28, 2006
  2. Jun 24, 2006
  3. Jun 23, 2006
  4. Jun 22, 2006
    • Daniel Stenberg's avatar
      Peter Silva introduced CURLOPT_MAX_SEND_SPEED_LARGE and · dfe1884c
      Daniel Stenberg authored
      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.
      dfe1884c
  5. Jun 19, 2006
  6. Jun 12, 2006
  7. Jun 08, 2006
  8. Jun 07, 2006
  9. May 31, 2006
  10. May 25, 2006
  11. May 24, 2006
  12. May 10, 2006
  13. May 09, 2006
  14. May 08, 2006
  15. May 04, 2006
    • Daniel Stenberg's avatar
      Roland Blom filed bug report #1481217 · e85e3054
      Daniel Stenberg authored
      (http://curl.haxx.se/bug/view.cgi?id=1481217), with follow-ups by Michele Bini
      and David Byron. libcurl previously wrongly used GetLastError() on windows to
      get error details after socket-related function calls, when it really should
      use WSAGetLastError() instead.
      
      When changing to this, the former function Curl_ourerrno() is now instead
      called Curl_sockerrno() as it is necessary to only use it to get errno from
      socket-related functions as otherwise it won't work as intended on Windows.
      e85e3054
    • Daniel Stenberg's avatar
      Mark Eichin submitted bug report #1480821 · 758f6eed
      Daniel Stenberg authored
      (http://curl.haxx.se/bug/view.cgi?id=1480821) He found and identified a
      problem with how libcurl dealt with GnuTLS and a case where gnutls returned
      GNUTLS_E_AGAIN indicating it would block. It would then return an unexpected
      return code, making Curl_ssl_send() confuse the upper layer - causing random
      28 bytes trash data to get inserted in the transfered stream.
      
      The proper fix was to make the Curl_gtls_send() function return the proper
      return codes that the callers would expect. The Curl_ossl_send() function
      already did this.
      758f6eed
  16. May 02, 2006
  17. Apr 26, 2006
  18. Apr 25, 2006
  19. Apr 21, 2006
  20. Apr 18, 2006
  21. Apr 11, 2006
  22. Apr 10, 2006
  23. Apr 05, 2006
  24. Mar 28, 2006
  25. Mar 27, 2006
  26. Mar 26, 2006
  27. Mar 21, 2006
  28. Mar 20, 2006
  29. Mar 07, 2006