diff options
author | Jay Satiro <raysatiro@yahoo.com> | 2020-04-04 16:16:18 -0400 |
---|---|---|
committer | Jay Satiro <raysatiro@yahoo.com> | 2020-05-12 03:00:15 -0400 |
commit | b995bb58cbd976280b132ee2148376fadd071063 (patch) | |
tree | 6e2c8903f3ae9e5bc515828df90f045dab186750 /docs/cmdline-opts | |
parent | 98e5904165859679cd78825bcccb52306ee3bb66 (diff) |
tool: Add option --retry-all-errors to retry on any error
The "sledgehammer" of retrying.
Closes https://github.com/curl/curl/pull/5185
Diffstat (limited to 'docs/cmdline-opts')
-rw-r--r-- | docs/cmdline-opts/Makefile.inc | 1 | ||||
-rw-r--r-- | docs/cmdline-opts/retry-all-errors.d | 19 |
2 files changed, 20 insertions, 0 deletions
diff --git a/docs/cmdline-opts/Makefile.inc b/docs/cmdline-opts/Makefile.inc index 5b7439e4a..6a7b953bc 100644 --- a/docs/cmdline-opts/Makefile.inc +++ b/docs/cmdline-opts/Makefile.inc @@ -180,6 +180,7 @@ DPAGES = \ request-target.d \ request.d \ resolve.d \ + retry-all-errors.d \ retry-connrefused.d \ retry-delay.d \ retry-max-time.d \ diff --git a/docs/cmdline-opts/retry-all-errors.d b/docs/cmdline-opts/retry-all-errors.d new file mode 100644 index 000000000..e0f662819 --- /dev/null +++ b/docs/cmdline-opts/retry-all-errors.d @@ -0,0 +1,19 @@ +Long: retry-all-errors +Help: Retry all errors (use with --retry) (read manpage, don't use by default) +Added: 7.71.0 +--- +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 don't parse or record output via redirect in combination with +this option, since you may receive duplicate data. |