1. 05 Sep, 2016 1 commit
  2. 04 Sep, 2016 1 commit
    • Olivier Brunel's avatar
      speed caps: not based on average speeds anymore · 4b86113f
      Olivier Brunel authored
      Speed limits (from CURLOPT_MAX_RECV_SPEED_LARGE &
      CURLOPT_MAX_SEND_SPEED_LARGE) were applied simply by comparing limits
      with the cumulative average speed of the entire transfer; While this
      might work at times with good/constant connections, in other cases it
      can result to the limits simply being "ignored" for more than "short
      bursts" (as told in man page).
      
      Consider a download that goes on much slower than the limit for some
      time (because bandwidth is used elsewhere, server is slow, whatever the
      reason), then once things get better, curl would simply ignore the limit
      up until the average speed (since the beginning of the transfer) reached
      the limit.  This could prove the limit useless to effectively avoid
      using the entire bandwidth (at least for quite some time).
      
      So instead, we now use a "moving starting point" as reference, and every
      time at least as much as the limit as been transferred, we can reset
      this starting point to the current position. This gets a good limiting
      effect that applies to the "current speed" with instant reactivity (in
      case of sudden speed burst).
      
      Closes #971
      4b86113f
  3. 03 Sep, 2016 3 commits
  4. 01 Sep, 2016 2 commits
  5. 31 Aug, 2016 4 commits
  6. 30 Aug, 2016 1 commit
  7. 29 Aug, 2016 1 commit
  8. 28 Aug, 2016 4 commits
  9. 27 Aug, 2016 2 commits
  10. 26 Aug, 2016 7 commits
  11. 25 Aug, 2016 5 commits
  12. 23 Aug, 2016 1 commit
    • Ales Novak's avatar
      ftp: fix wrong poll on the secondary socket · 7ad50a61
      Ales Novak authored
      
      
      When we're uploading using FTP and the server issues a tiny pause
      between opening the connection to the client's secondary socket, the
      client's initial poll() times out, which leads to second poll() which
      does not wait for POLLIN on the secondary socket. So that poll() also
      has to time out, creating a long (200ms) pause.
      
      This patch adds the correct flag to the secondary socket, making the
      second poll() correctly wait for the connection there too.
      
      Signed-off-by: default avatarAles Novak <alnovak@suse.cz>
      
      Closes #978
      7ad50a61
  13. 22 Aug, 2016 1 commit
  14. 21 Aug, 2016 6 commits
  15. 20 Aug, 2016 1 commit
    • Marc Hoersken's avatar
      socks.c: display the hostname returned by the SOCKS5 proxy server · b820e40f
      Marc Hoersken authored
      Instead of displaying the requested hostname the one returned
      by the SOCKS5 proxy server is used in case of connection error.
      The requested hostname is displayed earlier in the connection sequence.
      
      The upper-value of the port is moved to a temporary variable and
      replaced with a 0-byte to make sure the hostname is 0-terminated.
      b820e40f