Ignore:
Timestamp:
Sep 7, 2010, 4:46:12 AM (9 years ago)
Author:
julian.reschke@…
Message:

Uniform use of 'header field' (see #234)

File:
1 edited

Legend:

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

    r981 r994  
    334334<t>
    335335  If a range unit is not understood in a request, a server &MUST; ignore
    336   the whole Range header (<xref target="header.range" />).
     336  the whole Range header field (<xref target="header.range"/>).
    337337  If a range unit is not understood in a response, an intermediary
    338338  &SHOULD; pass the response to the client; a client &MUST; fail.
     
    403403<t>
    404404   A cache &MUST-NOT; combine a 206 response with other previously cached
    405    content if the ETag or Last-Modified headers do not match exactly,
     405   content if the ETag or Last-Modified header fields do not match exactly,
    406406   see <xref target="combining.byte.ranges"/>.
    407407</t>
    408408<t>
    409    A cache that does not support the Range and Content-Range headers
     409   A cache that does not support the Range and Content-Range header fields
    410410   &MUST-NOT; cache 206 (Partial Content) responses. Furthermore,
    411411   if a response uses a range unit that is not understood by the cache,
     
    492492<t>
    493493      but are not required to do so. Clients &MAY; generate range
    494       requests without having received this header for the resource
     494      requests without having received this header field for the resource
    495495      involved. Range units are defined in <xref target="range.units"/>.
    496496</t>
     
    546546</artwork></figure>
    547547<t>
    548    The header &SHOULD; indicate the total length of the full representation,
     548   The header field &SHOULD; indicate the total length of the full representation,
    549549   unless this length is unknown or difficult to determine. The asterisk
    550550   "*" character means that the instance-length is unknown at the time
     
    606606   example, a response to a request for a single range, or to a request
    607607   for a set of ranges that overlap without any holes), this content is
    608    transmitted with a Content-Range header, and a Content-Length header
    609    showing the number of bytes actually transferred. For example,
     608   transmitted with a Content-Range header field, and a Content-Length header
     609   field showing the number of bytes actually transferred. For example,
    610610</t>
    611611<figure><artwork type="example">
     
    655655    <x:h>Note:</x:h> Clients cannot depend on servers to send a 416 (Requested
    656656    range not satisfiable) response instead of a 200 (OK) response for
    657     an unsatisfiable Range request-header, since not all servers
    658     implement this request-header.
     657    an unsatisfiable Range request-header field, since not all servers
     658    implement this request-header field.
    659659  </t>
    660660</x:note>
     
    669669   If a client has a partial copy of a representation in its cache, and wishes
    670670   to have an up-to-date copy of the entire representation in its cache, it
    671    could use the Range request-header with a conditional GET (using
     671   could use the Range request-header field with a conditional GET (using
    672672   either or both of If-Unmodified-Since and If-Match.) However, if the
    673673   condition fails because the representation has been modified, the client
     
    687687<t>
    688688   If the client has no entity-tag for a representation, but does have a Last-Modified
    689    date, it &MAY; use that date in an If-Range header. (The
     689   date, it &MAY; use that date in an If-Range header field. (The
    690690   server can distinguish between a valid HTTP-date and any form of
    691691   entity-tag by examining no more than two characters.) The If-Range
    692    header &SHOULD; only be used together with a Range header, and &MUST; be
    693    ignored if the request does not include a Range header, or if the
     692   header field &SHOULD; only be used together with a Range header field, and &MUST; be
     693   ignored if the request does not include a Range header field, or if the
    694694   server does not support the sub-range operation.
    695695</t>
    696696<t>
    697    If the entity-tag given in the If-Range header matches the current
     697   If the entity-tag given in the If-Range header field matches the current
    698698   cache validator for the representation, then the server &SHOULD; provide the
    699699   specified sub-range of the representation using a 206 (Partial Content)
     
    840840</artwork></figure>
    841841<t>
    842    A server &MAY; ignore the Range header. However, HTTP/1.1 origin
     842   A server &MAY; ignore the Range header field. However, HTTP/1.1 origin
    843843   servers and intermediate caches ought to support byte ranges when
    844844   possible, since Range supports efficient recovery from partially
     
    847847</t>
    848848<t>
    849    If the server supports the Range header and the specified range or
     849   If the server supports the Range header field and the specified range or
    850850   ranges are appropriate for the representation:
    851851  <list style="symbols">
    852      <t>The presence of a Range header in an unconditional GET modifies
     852     <t>The presence of a Range header field in an unconditional GET modifies
    853853        what is returned if the GET is otherwise successful. In other
    854854        words, the response carries a status code of 206 (Partial
    855855        Content) instead of 200 (OK).</t>
    856856
    857      <t>The presence of a Range header in a conditional GET (a request
     857     <t>The presence of a Range header field in a conditional GET (a request
    858858        using one or both of If-Modified-Since and If-None-Match, or
    859859        one or both of If-Unmodified-Since and If-Match) modifies what
     
    865865<t>
    866866   In some cases, it might be more appropriate to use the If-Range
    867    header (see <xref target="header.if-range"/>) in addition to the Range header.
     867   header field (see <xref target="header.if-range"/>) in addition to the Range
     868   header field.
    868869</t>
    869870<t>
     
    14981499<section title="Since draft-ietf-httpbis-p5-range-02" anchor="changes.since.02">
    14991500<t>
    1500   Ongoing work on IANA Message Header Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
     1501  Ongoing work on IANA Message Header Field Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
    15011502  <list style="symbols">
    15021503    <t>
    1503       Reference RFC 3984, and update header registrations for headers defined
     1504      Reference RFC 3984, and update header field registrations for headers defined
    15041505      in this document.
    15051506    </t>
     
    15351536    <t>
    15361537      Rewrite ABNFs to spell out whitespace rules, factor out
    1537       header value format definitions.
     1538      header field value format definitions.
    15381539    </t>
    15391540  </list>
Note: See TracChangeset for help on using the changeset viewer.