From 15b8c6795ae0c2355784049690229924c4a47737 Mon Sep 17 00:00:00 2001 From: Jay Satiro Date: Fri, 31 Mar 2017 15:59:07 -0400 Subject: docs: Explain --fail-early does not imply --fail Closes https://github.com/curl/curl/pull/1375 --- docs/cmdline-opts/fail-early.d | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/cmdline-opts/fail-early.d b/docs/cmdline-opts/fail-early.d index 4489b4fc4..1bfaab4f3 100644 --- a/docs/cmdline-opts/fail-early.d +++ b/docs/cmdline-opts/fail-early.d @@ -2,7 +2,7 @@ Long: fail-early Help: Fail on first transfer error, do not continue Added: 7.52.0 --- -Fail and exit on first detected error. +Fail and exit on the first detected transfer error. When curl is used to do multiple transfers on the command line, it will attempt to operate on each given URL, one by one. By default, it will ignore @@ -15,4 +15,8 @@ that fails, independent on the amount of more URLs that are given on the command line. This way, no transfer failures go undetected by scripts and similar. -This option will apply for all given URLs even if you use --next. +This option is global and does not need to be specified for each use of --next. + +This option does not imply --fail, which causes transfers to fail due to the +server's HTTP status code. You can combine the two options, however note --fail +is not global and is therefore contained by --next. -- cgit v1.2.3