Ignore:
Timestamp:
Jul 10, 2012, 12:15:16 PM (8 years ago)
Author:
julian.reschke@…
Message:

insert paragraph breaks for readability

File:
1 edited

Legend:

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

    r1740 r1757  
    742742  <x:anchor-alias value="If-Match"/>
    743743<t>
    744    The "If-Match" header field can be used to make a request method
    745    conditional on the current existence or value of an entity-tag for
    746    one or more representations of the target resource.  If-Match is
    747    generally useful for resource update requests, such as PUT requests,
    748    as a means for protecting against accidental overwrites when multiple
    749    clients are acting in parallel on the same resource (i.e., the
     744   The "If-Match" header field can be used to make a request method conditional
     745   on the current existence or value of an entity-tag for one or more
     746   representations of the target resource.
     747</t>
     748<t>
     749   If-Match is generally useful for resource update requests, such as PUT
     750   requests, as a means for protecting against accidental overwrites when
     751   multiple clients are acting in parallel on the same resource (i.e., the
    750752   "lost update" problem).  An If-Match field-value of "*" places the
    751753   precondition on the existence of any current representation for the
     
    802804   The "If-None-Match" header field can be used to make a request method
    803805   conditional on not matching any of the current entity-tag values for
    804    representations of the target resource.  If-None-Match is primarily
    805    used in conditional GET requests to enable efficient updates of cached
    806    information with a minimum amount of transaction overhead.  A client
    807    that has one or more representations previously obtained from the
    808    target resource can send If-None-Match with a list of the associated
    809    entity-tags in the hope of receiving a <x:ref>304 (Not Modified)</x:ref>
    810    response if at least one of those representations matches the selected
    811    representation.
     806   representations of the target resource.
     807</t>
     808<t>
     809   If-None-Match is primarily used in conditional GET requests to enable
     810   efficient updates of cached information with a minimum amount of transaction
     811   overhead. A client that has one or more representations previously obtained
     812   from the target resource can send If-None-Match with a list of the
     813   associated entity-tags in the hope of receiving a <x:ref>304 (Not
     814   Modified)</x:ref> response if at least one of those representations matches
     815   the selected representation.
    812816</t>
    813817<t>
Note: See TracChangeset for help on using the changeset viewer.