mirror of
https://github.com/curl/curl.git
synced 2024-12-21 06:50:10 +08:00
2494b8dd51
- switch all invidual files documenting command line options into .md, as the documentation is now markdown-looking. - made the parser treat 4-space indents as quotes - switch to building the curl.1 manpage using the "mainpage.idx" file, which lists the files to include to generate it, instead of using the previous page-footer/headers. Also, those files are now also .md ones, using the same format. I gave them underscore prefixes to make them sort separately: _NAME.md, _SYNOPSIS.md, _DESCRIPTION.md, _URL.md, _GLOBBING.md, _VARIABLES.md, _OUTPUT.md, _PROTOCOLS.md, _PROGRESS.md, _VERSION.md, _OPTIONS.md, _FILES.md, _ENVIRONMENT.md, _PROXYPREFIX.md, _EXITCODES.md, _BUGS.md, _AUTHORS.md, _WWW.md, _SEEALSO.md - updated test cases accordingly Closes #12751
32 lines
1.1 KiB
Markdown
32 lines
1.1 KiB
Markdown
---
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: retry
|
|
Arg: <num>
|
|
Added: 7.12.3
|
|
Help: Retry request if transient problems occur
|
|
Category: curl
|
|
Multi: single
|
|
See-also:
|
|
- retry-max-time
|
|
Example:
|
|
- --retry 7 $URL
|
|
---
|
|
|
|
# `--retry`
|
|
|
|
If a transient error is returned when curl tries to perform a transfer, it
|
|
retries 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:
|
|
a timeout, an FTP 4xx response code or an HTTP 408, 429, 500, 502, 503 or 504
|
|
response code.
|
|
|
|
When curl is about to retry a transfer, it first waits one second and then for
|
|
all forthcoming retries it doubles the waiting time until it reaches 10
|
|
minutes which then remains 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.
|
|
|
|
curl complies with the Retry-After: response header if one was present to know
|
|
when to issue the next retry (added in 7.66.0).
|