Ignore:
Timestamp:
Mar 26, 2012, 9:27:31 AM (8 years ago)
Author:
ylafon@…
Message:

editorial changes (typos identified in <http://lists.w3.org/Archives/Public/ietf-http-wg/2012JanMar/0891.html>)

File:
1 edited

Legend:

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

    r1600 r1623  
    108108</t>
    109109<t>
    110    Part 5 defines range-specific requests and the rules for constructing and
     110   Part 5 defines range requests and the rules for constructing and
    111111   combining responses to those requests.
    112112</t>
     
    340340</t>
    341341<t>
    342    If the 206 response is the result of an If-Range request, the response
     342   If a 206 is sent in response to a request with an If-Range header field, it
    343343   &SHOULD-NOT; include other representation header fields. Otherwise, the response
    344344   &MUST; include all of the representation header fields that would have been returned
     
    412412<t>
    413413   A server &MAY; combine requested ranges when those ranges are overlapping
    414    (see <xref target="security.considerations"/>).
     414   (see <xref target="overlapping.ranges"/>).
    415415</t>
    416416<t>
     
    423423</t>
    424424<t>
    425    When a client requests multiple ranges in one request, the
     425   When a client asks for multiple ranges in one request, the
    426426   server &SHOULD; return them in the order that they appeared in the
    427427   request.
Note: See TracChangeset for help on using the changeset viewer.