romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-07-28 14:13:06 +03:00
Code Issues Projects Releases Packages Wiki Activity

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

Browse source 
Closes #6127
Fixes #6124
This commit is contained in:
José Joaquín Atria 2020-10-26 09:36:16 +00:00 • committed by Daniel Stenberg
parent bdbf82a9b7
commit 15ae039883
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
1 changed files with 2 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/cmdline-opts/range.d
View file

@ -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,