2016-11-28 07:50:25 +08:00
|
|
|
Long: retry
|
|
|
|
|
Arg: <num>
|
|
|
|
|
Added: 7.12.3
|
|
|
|
|
Help: Retry request if transient problems occur
|
|
|
|
|
---
|
|
|
|
|
If a transient error is returned when curl tries to perform a transfer, it
|
|
|
|
|
will retry this number of times before giving up. Setting the number to 0
|
|
|
|
|
makes curl do no retries (which is the default). Transient error means either:
|
2018-09-01 03:27:54 +08:00
|
|
|
a timeout, an FTP 4xx response code or an HTTP 408 or 5xx response code.
|
2016-11-28 07:50:25 +08:00
|
|
|
|
|
|
|
|
When curl is about to retry a transfer, it will first wait one second and then
|
|
|
|
|
for all forthcoming retries it will double the waiting time until it reaches
|
|
|
|
|
10 minutes which then will be the delay between the rest of the retries. By
|
|
|
|
|
using --retry-delay you disable this exponential backoff algorithm. See also
|
|
|
|
|
--retry-max-time to limit the total time allowed for retries.
|
|
|
|
|
|
2019-08-06 17:57:02 +08:00
|
|
|
Since curl 7.66.0, curl will comply with the Retry-After: response header if
|
|
|
|
|
one was present to know when to issue the next retry.
|
|
|
|
|
|
2016-11-28 07:50:25 +08:00
|
|
|
If this option is used several times, the last one will be used.
|
