Ignore:
Timestamp:
13/11/08 02:18:41 (12 years ago)
Author:
ylafon@…
Message:

expectation about support of range units by server/intermediaries/clients

File:
1 edited

Legend:

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

    r355 r358  
    299299</artwork></figure>
    300300<t>
    301    The only range unit defined by HTTP/1.1 is "bytes". HTTP/1.1
    302    implementations &MAY; ignore ranges specified using other units.
    303 </t>
    304 <t>
    305    HTTP/1.1 has been designed to allow implementations of applications
    306    that do not depend on knowledge of ranges.
     301  HTTP/1.1 has been designed to allow implementations of applications
     302  that do not depend on knowledge of ranges. The only range unit defined
     303  by HTTP/1.1 is "bytes".
     304</t>
     305<t>
     306  If a range unit is not understood in a request, a server &MUST; ignore
     307  the whole Range header (<xref target="header.range" />).
     308  If a range unit is not understood in a response, an intermediary
     309  &SHOULD; pass the response to the client; a client &MUST; fail.
    307310</t>
    308311</section>
Note: See TracChangeset for help on using the changeset viewer.