Closed mnot closed 3 years ago
Actually, it's not broken but somehow complicated due to the long qualification of what ranges this applies to ("that overlap or that are separated by a gap that is smaller than the overhead of sending multiple parts").
Maybe we should rephrase this.
normal
to easy
julian.reschke@gmx.de changed severity from In WG Last Call
to In IETF LC
unassigned
to 25
incorporated
new
to closed
http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p5-range-24.html#rfc.section.4.1:
"When multiple ranges are requested, a server MAY coalesce any of the ranges that overlap or that are separated by a gap that is smaller than the overhead of sending multiple parts, regardless of the order in which the corresponding byte-range-spec appeared in the received Range header field."
Reported by julian.reschke@gmx.de, migrated from https://trac.ietf.org/trac/httpbis/ticket/508