Opened 9 years ago
Closed 9 years ago
#508 closed editorial (incorporated)
broken sentence in description of 206
Reported by: | julian.reschke@… | Owned by: | draft-ietf-httpbis-p5-range@… |
---|---|---|---|
Priority: | easy | Milestone: | 25 |
Component: | p5-range | Severity: | In IETF LC |
Keywords: | Cc: |
Description
<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."
Change History (4)
comment:1 Changed 9 years ago by julian.reschke@…
- Priority changed from normal to easy
comment:2 Changed 9 years ago by julian.reschke@…
- Severity changed from In WG Last Call to In IETF LC
comment:3 Changed 9 years ago by fielding@…
comment:4 Changed 9 years ago by fielding@…
- Milestone changed from unassigned to 25
- Resolution set to incorporated
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
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.