aboutsummaryrefslogtreecommitdiff
path: root/docs/curl.1
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2006-10-25 20:40:14 +0000
committerDaniel Stenberg <daniel@haxx.se>2006-10-25 20:40:14 +0000
commitcde5e35d9b046b224c64936c432d67c9de8bcc9e (patch)
tree617d3c4165c5fcaa1eab9d8275ffe7e3dedfac60 /docs/curl.1
parentee17fba72e1525238a934118a348a241fb0f51ea (diff)
Fixed CURLOPT_FAILONERROR to return CURLE_HTTP_RETURNED_ERROR even for the
case when 401 or 407 are returned, *IF* no auth credentials have been given. The CURLOPT_FAILONERROR option is not possible to make fool-proof for 401 and 407 cases when auth credentials is given, but we've now covered this somewhat more. You might get some amounts of headers transferred before this situation is detected, like for when a "100-continue" is received as a response to a POST/PUT and a 401 or 407 is received immediately afterwards. Added test 281 to verify this change.
Diffstat (limited to 'docs/curl.1')
-rw-r--r--docs/curl.14
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/curl.1 b/docs/curl.1
index 24471d517..1305901b0 100644
--- a/docs/curl.1
+++ b/docs/curl.1
@@ -359,6 +359,10 @@ normal cases when a HTTP server fails to deliver a document, it returns an
HTML document stating so (which often also describes why and more). This flag
will prevent curl from outputting that and return error 22.
+This method is not fail-safe and there are occasions where non-succesful
+response codes will slip through, especially when authentication is involved
+(response codes 401 and 407).
+
If this option is used twice, the second will again disable silent failure.
.IP "--ftp-account [data]"
(FTP) When an FTP server asks for "account data" after user name and password