Skip to content
Snippets Groups Projects
  1. Dec 17, 2020
  2. Oct 10, 2020
  3. Sep 29, 2020
  4. Sep 27, 2020
  5. Sep 23, 2020
  6. Sep 22, 2020
  7. Sep 09, 2020
  8. Aug 09, 2020
  9. Mar 04, 2020
  10. Jan 29, 2019
  11. Oct 24, 2017
  12. Sep 30, 2017
    • Nat Goodspeed's avatar
      MAINT-7081: Eliminate unused variable errors after new refactoring. · 6b508cd9
      Nat Goodspeed authored
      The new helper functions check_curl_easy_setopt() and
      check_curl_multi_setopt() encapsulate the pervasive idiom:
      
          code = curl_{easy,multi}_setopt(handle, option, arg);
          check_curl_{easy,multi}_code(code, option);
      
      But since each of these helper functions contains its own local CURL{,M}code
      variable 'code', having a caller-scope variable reused for every such call is
      no longer necessary -- in fact is no longer used at all. That produces a fatal
      warning with MSVC. Get rid of those now-unused variables.
      6b508cd9
  13. Sep 29, 2017
  14. Aug 14, 2017
  15. Aug 08, 2017
  16. Jul 28, 2017
  17. Jul 24, 2017
  18. Dec 13, 2016
  19. Feb 19, 2016
  20. Nov 10, 2015
  21. Oct 16, 2015
  22. Aug 12, 2015
  23. Jul 08, 2015
  24. Jun 24, 2015
  25. Jun 05, 2015
  26. May 27, 2015
  27. Apr 10, 2015
  28. Apr 01, 2015
  29. Mar 27, 2015
  30. Mar 16, 2015
  31. Nov 06, 2014
    • Monty Brandenberg's avatar
      BUG-7698, BUG-7688, BUG-7694 (others) CDN connection issues. · de9689e3
      Monty Brandenberg authored
      Under pipelining, requests were given a 5x timeout factor due to the
      way that the timeout clock works in libcurl.  Under CDN load,
      connections were not being torn down quickly and it was only
      this timer that led to disconnect and retry.  So, we want to
      break a connection that isn't making progress but that isn't
      immediately possible.  We'll compromise with a 60S timeout that
      (we hope) will be neither too long for stalled connections nor
      too short for large asset transfer requests.
      de9689e3
  32. Oct 17, 2014
  33. Oct 10, 2014
  34. Sep 19, 2014
  35. Sep 18, 2014
  36. Sep 04, 2014
    • Monty Brandenberg's avatar
      Pipelining work. Extend transfer timeout by the pipeline depth · 0c20beda
      Monty Brandenberg authored
      as transfers can appear delayed with deep pipelining and more
      requests in the pool.  Added bad HTTP status error (typically
      getting a 0 back as HTTP status from libcurl) to the list of
      retryable errors.  There's a response stream problem with libcurl
      and pipelining that induces this problem.  Retrying helps but
      may not be entirely safe.  Watch bug 1420 on the libcurl sourceforge
      bug tracker.  Extend options of test/example program to include
      un-ranged requests.  Document the excessive data transfer induced
      when ranged requests are disabled.  This is an abnormal mode for
      very rare users so we'll just eat that for now.
      0c20beda
Loading