From: José Joaquín Atria <jjatria@gmail.com>
Date: Mon, 26 Oct 2020 09:36:16 +0000 (+0000)
Subject: range.d: clarify that curl will not parse multipart responses
X-Git-Tag: curl-7_74_0~131
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=15ae039;p=thirdparty%2Fcurl.git

range.d: clarify that curl will not parse multipart responses

Closes #6127
Fixes #6124
---

diff --git a/docs/cmdline-opts/range.d b/docs/cmdline-opts/range.d
index 17c6c2aba5..3dfa2f34c0 100644
--- a/docs/cmdline-opts/range.d
+++ b/docs/cmdline-opts/range.d
@@ -29,7 +29,8 @@ specifies two separate 100-byte ranges(*) (HTTP)
 .RE
 .IP
 (*) = NOTE that this will cause the server to reply with a multipart
-response!
+response, which will be retruned as-is by curl! Parsing or otherwise
+transforming this response is the responsibility of the caller.
 
 Only digit characters (0-9) are valid in the 'start' and 'stop' fields of the
 \&'start-stop' range syntax. If a non-digit character is given in the range,