Skip to content
  1. Sep 20, 2006
  2. Sep 12, 2006
  3. Sep 11, 2006
  4. Sep 10, 2006
  5. Sep 09, 2006
  6. Sep 08, 2006
  7. Sep 07, 2006
  8. Sep 04, 2006
  9. Sep 03, 2006
  10. Aug 31, 2006
  11. Aug 30, 2006
  12. Aug 29, 2006
  13. Aug 25, 2006
  14. Aug 22, 2006
  15. Aug 19, 2006
  16. Aug 18, 2006
  17. Aug 08, 2006
  18. Aug 07, 2006
  19. Aug 02, 2006
  20. Aug 01, 2006
  21. Jul 30, 2006
  22. Jul 27, 2006
  23. Jul 26, 2006
  24. Jul 25, 2006
  25. Jul 20, 2006
  26. Jul 17, 2006
  27. Jul 14, 2006
  28. Jul 08, 2006
  29. Jul 07, 2006
    • Daniel Stenberg's avatar
      Ingmar Runge provided a source snippet that caused a crash. The reason for · ca319f63
      Daniel Stenberg authored
      the crash was that libcurl internally was a bit confused about who owned the
      DNS cache at all times so if you created an easy handle that uses a shared
      DNS cache and added that to a multi handle it would crash. Now we keep more
      careful internal track of exactly what kind of DNS cache each easy handle
      uses: None, Private (allocated for and used only by this single handle),
      Shared (points to a cache held by a shared object), Global (points to the
      global cache) or Multi (points to the cache within the multi handle that is
      automatically shared between all easy handles that are added with private
      caches).
      ca319f63
  30. Jul 04, 2006
  31. Jun 24, 2006
  32. Jun 23, 2006
  33. 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
  34. Jun 19, 2006