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/p4-conditional.xml

    r981 r994  
    231231   A future draft will reorganize the sections to better reflect the content.
    232232   In particular, the sections on resource metadata will be discussed first
    233    and then followed by each conditional request-header, concluding with a
     233   and then followed by each conditional request-header field, concluding with a
    234234   definition of precedence and the expectation of ordering strong validator
    235235   checks before weak validator checks.  It is likely that more content from
    … …  
    573573  <list style="symbols">
    574574     <t>The validator is about to be used by a client in an If-Modified-Since
    575         or If-Unmodified-Since header, because the client
     575        or If-Unmodified-Since header field, because the client
    576576        has a cache entry for the associated representation, and</t>
    577577     <t>That cache entry includes a Date value, which gives the time
    … …  
    640640        unless the risk of a breakdown in semantic transparency that
    641641        could result from using this date in an If-Modified-Since header
    642         would lead to serious problems.</t>
     642        field would lead to serious problems.</t>
    643643  </list>
    644644</t>
    … …  
    764764   appropriate cache validation mechanism, and the specification of any
    765765   validator comparison function more complex than byte-equality would
    766    open up a can of worms. Thus, comparisons of any other headers
     766   open up a can of worms. Thus, comparisons of any other header fields
    767767   (except Last-Modified, for compatibility with HTTP/1.0) are never
    768768   used for purposes of validating a cache entry.
    … …  
    795795   If any of the entity-tags match the entity-tag of the representation that
    796796   would have been returned in the response to a similar GET request
    797    (without the If-Match header) on that resource, or if "*" is given
     797   (without the If-Match header field) on that resource, or if "*" is given
    798798   and any current representation exists for that resource, then the server &MAY;
    799799   perform the requested method as if the If-Match header field did not
    … …  
    810810<t>
    811811   If the request would, without the If-Match header field, result in
    812    anything other than a 2xx or 412 status code, then the If-Match header
     812   anything other than a 2xx or 412 status code, then the If-Match header field
    813813   &MUST; be ignored.
    814814</t>
    … …  
    864864</artwork></figure>
    865865<t>
    866    A GET method with an If-Modified-Since header and no Range header
    867    requests that the representation be transferred only if it has
    868    been modified since the date given by the If-Modified-Since header.
     866   A GET method with an If-Modified-Since header field and no Range header
     867   field requests that the representation be transferred only if it has
     868   been modified since the date given by the If-Modified-Since header field.
    869869   The algorithm for determining this includes the following cases:
    870870  <list style="numbers">
    … …  
    902902    </t><t>
    903903      <x:h>Note:</x:h> If a client uses an arbitrary date in the If-Modified-Since
    904       header instead of a date taken from the Last-Modified header for
     904      header field instead of a date taken from the Last-Modified header field for
    905905      the same request, the client needs to be aware that this
    906906      date is interpreted in the server's understanding of time.
    … …  
    954954   If any of the entity-tags match the entity-tag of the representation that
    955955   would have been returned in the response to a similar GET request
    956    (without the If-None-Match header) on that resource, or if "*" is
     956   (without the If-None-Match header field) on that resource, or if "*" is
    957957   given and any current representation exists for that resource, then the
    958958   server &MUST-NOT; perform the requested method, unless required to do
    … …  
    975975   If the request would, without the If-None-Match header field, result
    976976   in anything other than a 2xx or 304 status code, then the If-None-Match
    977    header &MUST; be ignored. (See <xref target="rules.for.when.to.use.entity.tags.and.last-modified.dates"/> for a discussion of
     977   header field &MUST; be ignored. (See <xref target="rules.for.when.to.use.entity.tags.and.last-modified.dates"/> for a discussion of
    978978   server behavior when both If-Modified-Since and If-None-Match appear
    979979   in the same request.)
    … …  
    10141014   in a 200 response to a GET request on the same resource has not been modified
    10151015   since the time specified in this field, the server &SHOULD; perform the
    1016    requested operation as if the If-Unmodified-Since header were not
     1016   requested operation as if the If-Unmodified-Since header field were not
    10171017   present.
    10181018</t>
    … …  
    10351035<t>
    10361036   If the request normally (i.e., without the If-Unmodified-Since
    1037    header) would result in anything other than a 2xx or 412 status code,
    1038    the If-Unmodified-Since header &SHOULD; be ignored.
    1039 </t>
    1040 <t>
    1041    If the specified date is invalid, the header is ignored.
     1037   header field) would result in anything other than a 2xx or 412 status code,
     1038   the If-Unmodified-Since header field &SHOULD; be ignored.
     1039</t>
     1040<t>
     1041   If the specified date is invalid, the header field is ignored.
    10421042</t>
    10431043<t>
    … …  
    15851585</t>
    15861586<t>
    1587   Ongoing work on IANA Message Header Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
     1587  Ongoing work on IANA Message Header Field Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
    15881588  <list style="symbols">
    15891589    <t>
    1590       Reference RFC 3984, and update header registrations for headers defined
     1590      Reference RFC 3984, and update header field registrations for header fields defined
    15911591      in this document.
    15921592    </t>
    … …  
    16281628    <t>
    16291629      Rewrite ABNFs to spell out whitespace rules, factor out
    1630       header value format definitions.
     1630      header field value format definitions.
    16311631    </t>
    16321632  </list>
Note: See TracChangeset for help on using the changeset viewer.