Skip to content
Snippets Groups Projects
  1. Jul 20, 2007
  2. Jul 18, 2007
  3. Jul 11, 2007
  4. Jul 02, 2007
  5. Jul 01, 2007
  6. Jun 27, 2007
  7. Jun 13, 2007
  8. May 30, 2007
  9. May 15, 2007
  10. May 08, 2007
  11. May 03, 2007
  12. Mar 23, 2007
  13. Mar 12, 2007
  14. Mar 11, 2007
  15. Mar 10, 2007
  16. Feb 22, 2007
  17. Feb 20, 2007
  18. Feb 12, 2007
  19. Feb 05, 2007
    • Daniel Stenberg's avatar
      - Michael Wallner provided a patch that adds support for CURLOPT_TIMEOUT_MS · 91386937
      Daniel Stenberg authored
        and CURLOPT_CONNECTTIMEOUT_MS that, as their names should hint, do the
        timeouts with millisecond resolution instead. The only restriction to that
        is the alarm() (sometimes) used to abort name resolves as that uses full
        seconds. I fixed the FTP response timeout part of the patch.
      
        Internally we now count and keep the timeouts in milliseconds but it also
        means we multiply set timeouts with 1000. The effect of this is that no
        timeout can be set to more than 2^31 milliseconds (on 32 bit systems), which
        equals 24.86 days.  We probably couldn't before either since the code did
        *1000 on the timeout values on several places already.
      91386937
  20. Jan 17, 2007
  21. Jan 05, 2007
  22. Dec 21, 2006
  23. Dec 05, 2006
  24. Nov 02, 2006
  25. Oct 25, 2006
    • Daniel Stenberg's avatar
      Fixed CURLOPT_FAILONERROR to return CURLE_HTTP_RETURNED_ERROR even for the · cde5e35d
      Daniel Stenberg authored
      case when 401 or 407 are returned, *IF* no auth credentials have been given.
      The CURLOPT_FAILONERROR option is not possible to make fool-proof for 401
      and 407 cases when auth credentials is given, but we've now covered this
      somewhat more.
      
      You might get some amounts of headers transferred before this situation is
      detected, like for when a "100-continue" is received as a response to a
      POST/PUT and a 401 or 407 is received immediately afterwards.
      
      Added test 281 to verify this change.
      cde5e35d
  26. Sep 30, 2006
  27. Sep 26, 2006
  28. Sep 11, 2006
  29. Sep 08, 2006
  30. Aug 29, 2006
  31. Aug 23, 2006
  32. Aug 09, 2006
  33. Aug 08, 2006
  34. Aug 02, 2006
  35. Jul 25, 2006
  36. 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
Loading