From 15ae039883546abc9b338b1583eed5c41fd38ace Mon Sep 17 00:00:00 2001 From: =?utf8?q?Jos=C3=A9=20Joaqu=C3=ADn=20Atria?= Date: Mon, 26 Oct 2020 09:36:16 +0000 Subject: [PATCH] range.d: clarify that curl will not parse multipart responses Closes #6127 Fixes #6124 --- docs/cmdline-opts/range.d | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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, -- 2.47.3