Ignore:
Timestamp:
Mar 10, 2011, 10:45:30 PM (9 years ago)
Author:
fielding@…
Message:

Remove header field classifications.

Addresses #224 and #104

File:
1 edited

Legend:

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

    r1145 r1163  
    417417<t>
    418418   A server &SHOULD; return a response with this status code if a request
    419    included a Range request-header field (<xref target="header.range"/>), and none of
     419   included a Range header field (<xref target="header.range"/>), and none of
    420420   the ranges-specifier values in this field overlap the current extent
    421421   of the selected resource, and the request did not include an If-Range
    422    request-header field (<xref target="header.if-range"/>). (For byte-ranges,
     422   header field (<xref target="header.if-range"/>). (For byte-ranges,
    423423   this means that the first-byte-pos of all of the byte-range-spec values were
    424424   greater than the current length of the selected resource.)
     
    474474  <x:anchor-alias value="acceptable-ranges"/>
    475475<t>
    476    The "Accept-Ranges" response-header field allows a resource to indicate
     476   The "Accept-Ranges" header field allows a resource to indicate
    477477   its acceptance of range requests.
    478478</t>
     
    643643<t>
    644644   If the server receives a request (other than one including an If-Range
    645    request-header field) with an unsatisfiable Range request-header
     645   header field) with an unsatisfiable Range header
    646646   field (that is, all of whose byte-range-spec values have a
    647647   first-byte-pos value greater than the current length of the selected
     
    653653    <x:h>Note:</x:h> Clients cannot depend on servers to send a 416 (Requested
    654654    range not satisfiable) response instead of a 200 (OK) response for
    655     an unsatisfiable Range request-header field, since not all servers
    656     implement this request-header field.
     655    an unsatisfiable Range header field, since not all servers
     656    implement this header field.
    657657  </t>
    658658</x:note>
     
    667667   If a client has a partial copy of a representation in its cache, and wishes
    668668   to have an up-to-date copy of the entire representation in its cache, it
    669    could use the Range request-header field with a conditional GET (using
     669   could use the Range header field with a conditional GET (using
    670670   either or both of If-Unmodified-Since and If-Match.) However, if the
    671671   condition fails because the representation has been modified, the client
     
    674674</t>
    675675<t>
    676    The "If-Range" request-header field allows a client to "short-circuit" the second
     676   The "If-Range" header field allows a client to "short-circuit" the second
    677677   request. Informally, its meaning is "if the representation is unchanged, send
    678678   me the part(s) that I am missing; otherwise, send me the entire new
     
    826826  <x:anchor-alias value="other-range-set"/>
    827827<t>
    828    The "Range" request-header field defines the GET method (conditional or
     828   The "Range" header field defines the GET method (conditional or
    829829   not) to request one or more sub-ranges of the response representation body, instead
    830830   of the entire representation body.
Note: See TracChangeset for help on using the changeset viewer.