curl/docs/cmdline-opts/retry-all-errors.d

Long: retry-all-errors
Help: Retry all errors (use with --retry)
Added: 7.71.0
Category: curl
Example: --retry-all-errors $URL
See-also: retry
---
Retry on any error. This option is used together with --retry.

This option is the "sledgehammer" of retrying. Do not use this option by
default (eg in curlrc), there may be unintended consequences such as sending or
receiving duplicate data. Do not use with redirected input or output. You'd be
much better off handling your unique problems in shell script. Please read the
example below.

**WARNING**: For server compatibility curl attempts to retry failed flaky
transfers as close as possible to how they were started, but this is not
possible with redirected input or output. For example, before retrying it
removes output data from a failed partial transfer that was written to an
output file. However this is not true of data redirected to a | pipe or >
file, which are not reset. We strongly suggest you do not parse or record
output via redirect in combination with this option, since you may receive
duplicate data.

By default curl will not error on an HTTP response code that indicates an HTTP
error, if the transfer was successful. For example, if a server replies 404
Not Found and the reply is fully received then that is not an error. When
--retry is used then curl will retry on some HTTP response codes that indicate
transient HTTP errors, but that does not include most 4xx response codes such
as 404. If you want to retry on all response codes that indicate HTTP errors
(4xx and 5xx) then combine with --fail.
tool: Add option --retry-all-errors to retry on any error The "sledgehammer" of retrying. Closes https://github.com/curl/curl/pull/5185 2020-04-05 04:16:18 +08:00			`Long: retry-all-errors`
retry-all-errors.d: Shorten the summary line Follow-up to b995bb5 from a few moments ago. Reported-by: Daniel Stenberg Ref: https://github.com/curl/curl/commit/b995bb5#r39108929 2020-05-12 15:12:13 +08:00			`Help: Retry all errors (use with --retry)`
tool: Add option --retry-all-errors to retry on any error The "sledgehammer" of retrying. Closes https://github.com/curl/curl/pull/5185 2020-04-05 04:16:18 +08:00			`Added: 7.71.0`
docs: add categories to all cmdline opts Adapted gen.pl with 'listcats' This commit is a part of "--help me if you can" Closes #5680 2020-07-13 20:15:04 +08:00			`Category: curl`
curl.1: provide examples for each option The file format for each option now features a "Example:" header that can provide one or more examples that get rendered appropriately in the output. All options MUST have at least one example or gen.pl complains at build-time. This fix also does a few other minor format and consistency cleanups. Closes #7654 2021-08-31 22:37:14 +08:00			`Example: --retry-all-errors $URL`
curl.1: require "see also" for every documented option gen.pl now generates a warning if the "See Also" field is not filled in for a command line option All command line options now provide one or more related options. 167 "See alsos" added! Closes #8019 2021-11-15 22:58:20 +08:00			`See-also: retry`
tool: Add option --retry-all-errors to retry on any error The "sledgehammer" of retrying. Closes https://github.com/curl/curl/pull/5185 2020-04-05 04:16:18 +08:00			`---`
			`Retry on any error. This option is used together with --retry.`

			`This option is the "sledgehammer" of retrying. Do not use this option by`
			`default (eg in curlrc), there may be unintended consequences such as sending or`
			`receiving duplicate data. Do not use with redirected input or output. You'd be`
			`much better off handling your unique problems in shell script. Please read the`
			`example below.`

curl.1: provide examples for each option The file format for each option now features a "Example:" header that can provide one or more examples that get rendered appropriately in the output. All options MUST have at least one example or gen.pl complains at build-time. This fix also does a few other minor format and consistency cleanups. Closes #7654 2021-08-31 22:37:14 +08:00			`WARNING: For server compatibility curl attempts to retry failed flaky`
			`transfers as close as possible to how they were started, but this is not`
			`possible with redirected input or output. For example, before retrying it`
			`removes output data from a failed partial transfer that was written to an`
			`output file. However this is not true of data redirected to a \| pipe or >`
docs: reduce/avoid English contractions You're => You are Hasn't => Has not Doesn't => Does not Don't => Do not You'll => You will etc Closes #7930 2021-10-31 23:34:44 +08:00			`file, which are not reset. We strongly suggest you do not parse or record`
			`output via redirect in combination with this option, since you may receive`
			`duplicate data.`
retry-all-errors.d: Explain curl errors versus HTTP response errors - Add a paragraph explaining that curl does not consider HTTP response errors as curl errors, and how that behavior can be modified by using --retry and --fail. The --retry-all-errors doc says "Retry on any error" which some users may find misleading without the added explanation. Ref: https://curl.se/docs/faq.html#Why_do_I_get_downloaded_data_eve Ref: https://curl.se/docs/faq.html#curl_doesn_t_return_error_for_HT Reported-by: Lawrence Gripper Fixes https://github.com/curl/curl/issues/6712 Closes https://github.com/curl/curl/pull/6720 2021-03-11 15:36:37 +08:00
			`By default curl will not error on an HTTP response code that indicates an HTTP`
			`error, if the transfer was successful. For example, if a server replies 404`
			`Not Found and the reply is fully received then that is not an error. When`
			`--retry is used then curl will retry on some HTTP response codes that indicate`
			`transient HTTP errors, but that does not include most 4xx response codes such`
			`as 404. If you want to retry on all response codes that indicate HTTP errors`
			`(4xx and 5xx) then combine with --fail.`