From: Daniel Stenberg <daniel@haxx.se>
Date: Tue, 19 May 2020 07:42:11 +0000 (+0200)
Subject: TODO: Ratelimit or wait between serial requests
X-Git-Tag: curl-7_71_0~121
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=39177b8ef9c42e9f2892aad57ede70d5eb556cc3;p=thirdparty%2Fcurl.git

TODO: Ratelimit or wait between serial requests

Closes #5406
---

diff --git a/docs/TODO b/docs/TODO
index e6d209bc9a..fe3a3ab228 100644
--- a/docs/TODO
+++ b/docs/TODO
@@ -148,6 +148,7 @@
  18.10 improve how curl works in a windows console window
  18.11 Windows: set attribute 'archive' for completed downloads
  18.12 keep running, read instructions from pipe/socket
+ 18.13 Ratelimit or wait between serial requests
  18.15 --retry should resume
  18.16 send only part of --data
  18.17 consider file name from the redirected URL with -O ?
@@ -1006,6 +1007,16 @@ that doesn't exist on the server, just like --ftp-create-dirs.
  invoke can talk to the still running instance and ask for transfers to get
  done, and thus maintain its connection pool, DNS cache and more.
 
+18.13 Ratelimit or wait between serial requests
+
+ Consider a command line option that can make curl do multiple serial requests
+ slow, potentially with a (random) wait between transfers. There's also a
+ propsed set of standard HTTP headers to let servers let the client adapt to
+ its rate limits:
+ https://www.ietf.org/id/draft-polli-ratelimit-headers-02.html
+
+ See https://github.com/curl/curl/issues/5406
+
 18.15 --retry should resume
 
  When --retry is used and curl actually retries transfer, it should use the