Mercurial > hgrepos > Python2 > PyMuPDF
comparison mupdf-source/thirdparty/curl/docs/cmdline-opts/retry.d @ 3:2c135c81b16c
MERGE: upstream PyMuPDF 1.26.4 with MuPDF 1.26.7
| author | Franz Glasner <fzglas.hg@dom66.de> |
|---|---|
| date | Mon, 15 Sep 2025 11:44:09 +0200 |
| parents | b50eed0cc0ef |
| children |
comparison
equal
deleted
inserted
replaced
| 0:6015a75abc2d | 3:2c135c81b16c |
|---|---|
| 1 Long: retry | |
| 2 Arg: <num> | |
| 3 Added: 7.12.3 | |
| 4 Help: Retry request if transient problems occur | |
| 5 --- | |
| 6 If a transient error is returned when curl tries to perform a transfer, it | |
| 7 will retry this number of times before giving up. Setting the number to 0 | |
| 8 makes curl do no retries (which is the default). Transient error means either: | |
| 9 a timeout, an FTP 4xx response code or an HTTP 408 or 5xx response code. | |
| 10 | |
| 11 When curl is about to retry a transfer, it will first wait one second and then | |
| 12 for all forthcoming retries it will double the waiting time until it reaches | |
| 13 10 minutes which then will be the delay between the rest of the retries. By | |
| 14 using --retry-delay you disable this exponential backoff algorithm. See also | |
| 15 --retry-max-time to limit the total time allowed for retries. | |
| 16 | |
| 17 Since curl 7.66.0, curl will comply with the Retry-After: response header if | |
| 18 one was present to know when to issue the next retry. | |
| 19 | |
| 20 If this option is used several times, the last one will be used. |
