]> git.ipfire.org Git - thirdparty/curl.git/commit
docs: better explain multi-part byte range behavior
authorJay Satiro <raysatiro@yahoo.com>
Sat, 1 Feb 2025 23:12:18 +0000 (18:12 -0500)
committerJay Satiro <raysatiro@yahoo.com>
Thu, 6 Feb 2025 08:09:45 +0000 (03:09 -0500)
commit3631c24861a96f252f6e5e89fb98b3a3e6c13850
treec6b82016e08197f7a95bc1803a58e3a8c0d6bc54
parent153453eb78d0767b1127f95be7d9d1f469e414ed
docs: better explain multi-part byte range behavior

- Better explain that if the requested range (--range or CURLOPT_RANGE)
  contains multiple ranges then the response contains meta information
  in addition to the requested bytes.

Prior to this change it was noted that a multiple part response was
returned as-is but not what that meant. In particular, meta information
is returned in addition to the requested bytes and that may have been
unexpected.

Reported-by: Ralf A. Timmermann
Fixes https://github.com/curl/curl/issues/16139
Closes https://github.com/curl/curl/pull/16150
docs/cmdline-opts/range.md
docs/libcurl/opts/CURLOPT_RANGE.md