summaryrefslogtreecommitdiff
path: root/docs/cmdline-opts/retry-all-errors.d
diff options
context:
space:
mode:
Diffstat (limited to 'docs/cmdline-opts/retry-all-errors.d')
-rw-r--r--docs/cmdline-opts/retry-all-errors.d16
1 files changed, 9 insertions, 7 deletions
diff --git a/docs/cmdline-opts/retry-all-errors.d b/docs/cmdline-opts/retry-all-errors.d
index 5ad1da0de..5cab5ddaa 100644
--- a/docs/cmdline-opts/retry-all-errors.d
+++ b/docs/cmdline-opts/retry-all-errors.d
@@ -2,6 +2,7 @@ Long: retry-all-errors
Help: Retry all errors (use with --retry)
Added: 7.71.0
Category: curl
+Example: --retry-all-errors $URL
---
Retry on any error. This option is used together with --retry.
@@ -11,13 +12,14 @@ 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.
+**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.
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