Ignore:
Timestamp:
Dec 31, 2012, 3:02:54 AM (7 years ago)
Author:
fielding@…
Message:

fix several more cases of include being used instead of send or generate, and a few requirements that are simply facts

File:
1 edited

Legend:

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

    r2069 r2073  
    522522   In the case of a byte range request:
    523523   a server sending a response with status code <x:ref>416 (Requested Range Not
    524    Satisfiable)</x:ref> &SHOULD; include a Content-Range field with a byte-range-resp-spec
     524   Satisfiable)</x:ref> &SHOULD; send a Content-Range field with a byte-range-resp-spec
    525525   of "*". The instance-length specifies the current length of
    526526   the selected resource. A response with status code <x:ref>206 (Partial Content)</x:ref>
    527    &MUST-NOT; include a Content-Range field with a byte-range-resp-spec of "*".
     527   &MUST-NOT; send a Content-Range field with a byte-range-resp-spec of "*".
    528528</t>
    529529<t>
Note: See TracChangeset for help on using the changeset viewer.