Ignore:
Timestamp:
Sep 26, 2009, 3:09:09 AM (10 years ago)
Author:
julian.reschke@…
Message:

editorial: enhance readability of header introductions

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r697 r698  
    689689<t>
    690690   The "ETag" response-header field provides the current value of the
    691    entity tag (see <xref target="entity.tags"/>) for the requested variant.
    692    The headers used with entity
    693    tags are described in Sections <xref target="header.if-match" format="counter"/>
    694    and <xref target="header.if-none-match" format="counter"/> of this document,
    695    and in &header-if-range;. The entity tag
    696    &MAY; be used for comparison with other entities from the same resource
     691   entity tag (see <xref target="entity.tags"/>) for the requested variant,
     692   which may be used for comparison with other entities from the same resource
    697693   (see <xref target="weak.and.strong.validators"/>).
    698694</t>
     
    734730  <x:anchor-alias value="If-Match-v"/>
    735731<t>
    736    The "If-Match" request-header field is used with a method to make it
     732   The "If-Match" request-header field is used to make a request method
    737733   conditional. A client that has one or more entities previously
    738734   obtained from the resource can verify that one of those entities is
    739735   current by including a list of their associated entity tags in the
    740    If-Match header field. Entity tags are defined in <xref target="entity.tags"/>. The
    741    purpose of this feature is to allow efficient updates of cached
    742    information with a minimum amount of transaction overhead. It is also
    743    used, on updating requests, to prevent inadvertent modification of
    744    the wrong version of a resource. As a special case, the value "*"
    745    matches any current entity of the resource.
     736   If-Match header field.
     737</t>
     738<t>
     739   This allows efficient updates of cached information with a minimum amount of
     740   transaction overhead. It is also used when updating resources, to prevent
     741   inadvertent modification of the wrong version of a resource. As a special
     742   case, the value "*" matches any current entity of the resource.
    746743</t>
    747744<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Match"/><iref primary="true" item="Grammar" subitem="If-Match-v"/>
     
    803800  <x:anchor-alias value="If-Modified-Since-v"/>
    804801<t>
    805    The "If-Modified-Since" request-header field is used with a method to
    806    make it conditional: if the requested variant has not been modified
    807    since the time specified in this field, an entity will not be
    808    returned from the server; instead, a 304 (Not Modified) response will
    809    be returned without any message-body.
     802   The "If-Modified-Since" request-header field is used to make a request
     803   method conditional: if the requested variant has not been modified since the
     804   time specified in this field, the server will not return an entity; instead,
     805   a 304 (Not Modified) response will be returned.
    810806</t>
    811807<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Modified-Since"/><iref primary="true" item="Grammar" subitem="If-Modified-Since-v"/>
     
    888884  <x:anchor-alias value="If-None-Match-v"/>
    889885<t>
    890    The "If-None-Match" request-header field is used with a method to make
    891    it conditional. A client that has one or more entities previously
     886   The "If-None-Match" request-header field is used to make a request method
     887   conditional. A client that has one or more entities previously
    892888   obtained from the resource can verify that none of those entities is
    893889   current by including a list of their associated entity tags in the
    894    If-None-Match header field. The purpose of this feature is to allow
    895    efficient updates of cached information with a minimum amount of
     890   If-None-Match header field.
     891</t>
     892<t>
     893   This allows efficient updates of cached information with a minimum amount of
    896894   transaction overhead. It is also used to prevent a method (e.g. PUT)
    897895   from inadvertently modifying an existing resource when the client
     
    965963  <x:anchor-alias value="If-Unmodified-Since-v"/>
    966964<t>
    967    The "If-Unmodified-Since" request-header field is used with a method to
    968    make it conditional. If the requested resource has not been modified
     965   The "If-Unmodified-Since" request-header field is used to make a request
     966   method conditional. If the requested resource has not been modified
    969967   since the time specified in this field, the server &SHOULD; perform the
    970968   requested operation as if the If-Unmodified-Since header were not
Note: See TracChangeset for help on using the changeset viewer.