Ignore:
Timestamp:
12/06/13 19:22:19 (7 years ago)
Author:
fielding@…
Message:

(editorial) clients do not generate entity-tags, so rephrase [2290] so that the requirement is on generating the field; addresses #485

File:
1 edited

Legend:

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

    r2290 r2292  
    465465</artwork></figure>
    466466<t>
    467    Clients &MUST-NOT; generate an entity-tag marked as weak in an If-Range
    468    field value and &MUST-NOT; generate a <x:ref>Last-Modified</x:ref> date in an
    469    If-Range field value unless it has no entity-tag for the representation and
    470    the Last-Modified date it does have for the representation is strong
     467   A client &MUST-NOT; generate an If-Range header field containing an
     468   entity-tag that is marked as weak.
     469   A client &MUST-NOT; generate an If-Range header field containing a
     470   <x:ref>Last-Modified</x:ref> date unless the client has no entity-tag for
     471   the corresponding representation and the Last-Modified date is strong
    471472   in the sense defined by &lastmod-comparison;.
    472473</t>
     
    585586   only one range remained after coalescing.
    586587   A client that cannot process a multipart/byteranges response &MUST-NOT;
    587    generate requests asking for multiple ranges in one single request.
     588   generate a request that asks for multiple ranges.
    588589</t>
    589590<t>
Note: See TracChangeset for help on using the changeset viewer.