Ignore:
Timestamp:
15/09/13 02:23:08 (7 years ago)
Author:
fielding@…
Message:

uniform terminology for private cache (not non-shared), user agent, and avoid plural subjects in requirements; clarify that recipients don't have to parse all received URIs; addresses #234

File:
1 edited

Legend:

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

    r2401 r2402  
    344344</artwork></figure>
    345345<t>
    346    Origin servers that support byte-range requests &MAY; send
     346   An origin server that supports byte-range requests for a given target
     347   resource &MAY; send
    347348</t>
    348349<figure><artwork type="example">
     
    350351</artwork></figure>
    351352<t>
    352    but are not required to do so. Clients &MAY; generate range
     353   to indicate what range units are supported. A client &MAY; generate range
    353354   requests without having received this header field for the resource
    354355   involved. Range units are defined in <xref target="range.units"/>.
    355356</t>
    356357<t>
    357    Servers that do not support any kind of range request for the target
     358   A server that does not support any kind of range request for the target
    358359   resource resource &MAY; send
    359360</t>
Note: See TracChangeset for help on using the changeset viewer.