Ignore:
Timestamp:
20/06/13 16:41:11 (7 years ago)
Author:
julian.reschke@…
Message:

adjust language describing why a server would not return 416, also s/record/process/ because we never say what "record" means (see #462)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r2296 r2297  
    781781   content ranges in the new response and each of the selected responses.
    782782   If the union consists of the entire range of the representation, then the
    783    client &MUST; record the combined response as if it were a complete
     783   client &MUST; process the combined response as if it were a complete
    784784   <x:ref>200 (OK)</x:ref> response, including a <x:ref>Content-Length</x:ref>
    785785   header field that reflects the complete length.
    786    Otherwise, the client &MUST; record the set of continuous ranges as one of
     786   Otherwise, the client &MUST; process the set of continuous ranges as one of
    787787   the following:
    788788   an incomplete <x:ref>200 (OK)</x:ref> response if the combined response is
     
    826826    &Note; Because servers are free to ignore <x:ref>Range</x:ref>, many
    827827    implementations will simply respond with the entire selected representation
    828     in a <x:ref>200 (OK)</x:ref> response if the
    829     requested ranges are invalid or not satisfiable. That is partly because
     828    in a <x:ref>200 (OK)</x:ref> response. That is partly because
    830829    most clients are prepared to receive a <x:ref>200 (OK)</x:ref> to
    831830    complete the task (albeit less efficiently) and partly because clients
Note: See TracChangeset for help on using the changeset viewer.