romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-07-24 11:37:21 +03:00
Code Issues Projects Releases Packages Wiki Activity

tool: Add option --retry-all-errors to retry on any error

Browse source 
The "sledgehammer" of retrying.

Closes https://github.com/curl/curl/pull/5185
This commit is contained in:
Jay Satiro 2020-04-04 16:16:18 -04:00
parent 98e5904165
commit b995bb58cb
8 changed files with 98 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

1
docs/cmdline-opts/Makefile.inc
View file

@ -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 \

19
docs/cmdline-opts/retry-all-errors.d Normal file
View file

@ -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.