range.d: clarify that curl will not parse multipart responses
Closes #6127 Fixes #6124
This commit is contained in:
parent
bdbf82a9b7
commit
15ae039883
@ -29,7 +29,8 @@ specifies two separate 100-byte ranges(*) (HTTP)
|
|||||||
.RE
|
.RE
|
||||||
.IP
|
.IP
|
||||||
(*) = NOTE that this will cause the server to reply with a multipart
|
(*) = 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
|
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,
|
\&'start-stop' range syntax. If a non-digit character is given in the range,
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user