Ignore:
Timestamp:
21/01/13 07:43:33 (8 years ago)
Author:
fielding@…
Message:

(editorial) Fix a few cases where the term payload is used beyond the scope of a message

File:
1 edited

Legend:

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

    r2145 r2147  
    316316   <x:ref>last-byte-pos</x:ref>, and <x:ref>suffix-length</x:ref> are
    317317   expressed as decimal number of octets.  Since there is no predefined limit
    318    to the length of an HTTP payload, recipients &SHOULD; anticipate
     318   to the length of a payload, recipients &SHOULD; anticipate
    319319   potentially large decimal numerals and prevent parsing errors due to integer
    320320   conversion overflows.
     
    624624<t>
    625625   The "Content-Range" header field is sent with a partial representation to
    626    specify where in the full representation the payload body is intended to be
    627    applied.
     626   specify what range of the full representation is enclosed as payload.
    628627</t>
    629628<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Range"/><iref primary="true" item="Grammar" subitem="byte-content-range"/><iref primary="true" item="Grammar" subitem="byte-range-resp"/><iref primary="true" item="Grammar" subitem="byte-range"/><iref primary="true" item="Grammar" subitem="unsatisfied-range"/><iref primary="true" item="Grammar" subitem="other-content-range"/><iref primary="true" item="Grammar" subitem="other-range-resp"/><iref primary="true" item="Grammar" subitem="complete-length"/>
Note: See TracChangeset for help on using the changeset viewer.