Ignore:
Timestamp:
Dec 16, 2012, 4:26:52 PM (7 years ago)
Author:
fielding@…
Message:

oops, fix a few phrasing of return vs send due to last commit

File:
1 edited

Legend:

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

    r2052 r2053  
    296296</t>
    297297<t>
    298    When this status code is sent for a byte-range request, the
     298   When this status code is sent in response to a byte-range request, the
    299299   response &SHOULD; include a <x:ref>Content-Range</x:ref> header field
    300300   specifying the current length of the representation (see <xref target="header.content-range"/>).
    301    This response &MUST-NOT; use the multipart/byteranges content-type.
     301   This response &MUST-NOT; use the multipart/byteranges media type.
    302302</t>
    303303<figure>
     
    13071307</t>
    13081308<t>
    1309   Servers are given more leeway in what they send to a range request,
    1310   in order to mitigate malicious (or just greedy) clients.
     1309  Servers are given more leeway in how they respond to a range request,
     1310  in order to mitigate abuse by malicious (or just greedy) clients.
    13111311</t>
    13121312<t>
Note: See TracChangeset for help on using the changeset viewer.