Changeset 1757


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

insert paragraph breaks for readability

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r1756 r1757  
    968968      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.if-match" href="#header.if-match">If-Match</a></h2>
    969969      <p id="rfc.section.3.1.p.1">The "If-Match" header field can be used to make a request method conditional on the current existence or value of an entity-tag
    970          for one or more representations of the target resource. If-Match is generally useful for resource update requests, such as
    971          PUT requests, as a means for protecting against accidental overwrites when multiple clients are acting in parallel on the
    972          same resource (i.e., the "lost update" problem). An If-Match field-value of "*" places the precondition on the existence of
    973          any current representation for the target resource.
     970         for one or more representations of the target resource.
     971      </p>
     972      <p id="rfc.section.3.1.p.2">If-Match is generally useful for resource update requests, such as PUT requests, as a means for protecting against accidental
     973         overwrites when multiple clients are acting in parallel on the same resource (i.e., the "lost update" problem). An If-Match
     974         field-value of "*" places the precondition on the existence of any current representation for the target resource.
    974975      </p>
    975976      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.if-match" class="smpl">If-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a>
    976 </pre><p id="rfc.section.3.1.p.3">If any of the entity-tags listed in the If-Match field value match (as per <a href="#entity.tag.comparison" title="Comparison">Section&nbsp;2.3.2</a>) the entity-tag of the selected representation for the target resource, or if "*" is given and any current representation
     977</pre><p id="rfc.section.3.1.p.4">If any of the entity-tags listed in the If-Match field value match (as per <a href="#entity.tag.comparison" title="Comparison">Section&nbsp;2.3.2</a>) the entity-tag of the selected representation for the target resource, or if "*" is given and any current representation
    977978         exists for the target resource, then the server <em class="bcp14">MAY</em> perform the request method as if the If-Match header field was not present.
    978979      </p>
    979       <p id="rfc.section.3.1.p.4">Origin servers <em class="bcp14">MUST NOT</em> perform the requested method if none of the entity-tags match, or if "*" is given and no current representation exists; instead
     980      <p id="rfc.section.3.1.p.5">Origin servers <em class="bcp14">MUST NOT</em> perform the requested method if none of the entity-tags match, or if "*" is given and no current representation exists; instead
    980981         they <em class="bcp14">MUST</em> respond with the <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code.
    981982      </p>
    982       <p id="rfc.section.3.1.p.5">Proxy servers using a cached response as the selected representation <em class="bcp14">MUST NOT</em> perform the requested method if none of the entity-tags match, or if "*" is given and no current representation exists; instead,
     983      <p id="rfc.section.3.1.p.6">Proxy servers using a cached response as the selected representation <em class="bcp14">MUST NOT</em> perform the requested method if none of the entity-tags match, or if "*" is given and no current representation exists; instead,
    983984         they <em class="bcp14">MUST</em> forward the request towards the origin server.
    984985      </p>
    985       <p id="rfc.section.3.1.p.6">If the request would, without the If-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code, then the If-Match header field <em class="bcp14">MUST</em> be ignored.
    986       </p>
    987       <p id="rfc.section.3.1.p.7">Examples:</p>
     986      <p id="rfc.section.3.1.p.7">If the request would, without the If-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code, then the If-Match header field <em class="bcp14">MUST</em> be ignored.
     987      </p>
     988      <p id="rfc.section.3.1.p.8">Examples:</p>
    988989      <div id="rfc.figure.u.10"></div><pre class="text">  If-Match: "xyzzy"
    989990  If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
    990991  If-Match: *
    991 </pre><p id="rfc.section.3.1.p.9">The result of a request having both an If-Match header field and either an <a href="#header.if-none-match" class="smpl">If-None-Match</a> or an <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> header field is undefined by this specification.
     992</pre><p id="rfc.section.3.1.p.10">The result of a request having both an If-Match header field and either an <a href="#header.if-none-match" class="smpl">If-None-Match</a> or an <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> header field is undefined by this specification.
    992993      </p>
    993994      <div id="rfc.iref.i.2"></div>
     
    995996      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.if-none-match" href="#header.if-none-match">If-None-Match</a></h2>
    996997      <p id="rfc.section.3.2.p.1">The "If-None-Match" header field can be used to make a request method conditional on not matching any of the current entity-tag
    997          values for representations of the target resource. If-None-Match is primarily used in conditional GET requests to enable efficient
    998          updates of cached information with a minimum amount of transaction overhead. A client that has one or more representations
    999          previously obtained from the target resource can send If-None-Match with a list of the associated entity-tags in the hope
    1000          of receiving a <a href="#status.304" class="smpl">304 (Not Modified)</a> response if at least one of those representations matches the selected representation.
    1001       </p>
    1002       <p id="rfc.section.3.2.p.2">If-None-Match can also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying
     998         values for representations of the target resource.
     999      </p>
     1000      <p id="rfc.section.3.2.p.2">If-None-Match is primarily used in conditional GET requests to enable efficient updates of cached information with a minimum
     1001         amount of transaction overhead. A client that has one or more representations previously obtained from the target resource
     1002         can send If-None-Match with a list of the associated entity-tags in the hope of receiving a <a href="#status.304" class="smpl">304 (Not
     1003            Modified)</a> response if at least one of those representations matches the selected representation.
     1004      </p>
     1005      <p id="rfc.section.3.2.p.3">If-None-Match can also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying
    10031006         an existing representation of the target resource when the client believes that the resource does not have a current representation.
    10041007         This is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial representation
     
    10061009      </p>
    10071010      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#header.if-none-match" class="smpl">If-None-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a>
    1008 </pre><p id="rfc.section.3.2.p.4">If any of the entity-tags listed in the If-None-Match field-value match (as per <a href="#entity.tag.comparison" title="Comparison">Section&nbsp;2.3.2</a>) the entity-tag of the selected representation, or if "*" is given and any current representation exists for that resource,
     1011</pre><p id="rfc.section.3.2.p.5">If any of the entity-tags listed in the If-None-Match field-value match (as per <a href="#entity.tag.comparison" title="Comparison">Section&nbsp;2.3.2</a>) the entity-tag of the selected representation, or if "*" is given and any current representation exists for that resource,
    10091012         then the server <em class="bcp14">MUST NOT</em> perform the requested method. Instead, if the request method was GET or HEAD, the server <em class="bcp14">SHOULD</em> respond with a <a href="#status.304" class="smpl">304 (Not Modified)</a> status code, including the cache-related header fields (particularly <a href="#header.etag" class="smpl">ETag</a>) of the selected representation that has a matching entity-tag. For all other request methods, the server <em class="bcp14">MUST</em> respond with a <a href="#status.412" class="smpl">412 (Precondition Failed)</a> status code.
    10101013      </p>
    1011       <p id="rfc.section.3.2.p.5">If none of the entity-tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> header field(s) in the request. That is, if no entity-tags match, then the server <em class="bcp14">MUST NOT</em> return a <a href="#status.304" class="smpl">304 (Not Modified)</a> response.
    1012       </p>
    1013       <p id="rfc.section.3.2.p.6">If the request would, without the If-None-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="#status.304" class="smpl">304 (Not Modified)</a> status code, then the If-None-Match header field <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section&nbsp;2.4</a> for a discussion of server behavior when both <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> and If-None-Match appear in the same request.)
    1014       </p>
    1015       <p id="rfc.section.3.2.p.7">Examples:</p>
     1014      <p id="rfc.section.3.2.p.6">If none of the entity-tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> header field(s) in the request. That is, if no entity-tags match, then the server <em class="bcp14">MUST NOT</em> return a <a href="#status.304" class="smpl">304 (Not Modified)</a> response.
     1015      </p>
     1016      <p id="rfc.section.3.2.p.7">If the request would, without the If-None-Match header field, result in anything other than a <a href="p2-semantics.html#status.2xx" class="smpl">2xx (Successful)</a> or <a href="#status.304" class="smpl">304 (Not Modified)</a> status code, then the If-None-Match header field <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section&nbsp;2.4</a> for a discussion of server behavior when both <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> and If-None-Match appear in the same request.)
     1017      </p>
     1018      <p id="rfc.section.3.2.p.8">Examples:</p>
    10161019      <div id="rfc.figure.u.12"></div><pre class="text">  If-None-Match: "xyzzy"
    10171020  If-None-Match: W/"xyzzy"
     
    10191022  If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz"
    10201023  If-None-Match: *
    1021 </pre><p id="rfc.section.3.2.p.9">The result of a request having both an If-None-Match header field and either an <a href="#header.if-match" class="smpl">If-Match</a> or an <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> header field is undefined by this specification.
     1024</pre><p id="rfc.section.3.2.p.10">The result of a request having both an If-None-Match header field and either an <a href="#header.if-match" class="smpl">If-Match</a> or an <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> header field is undefined by this specification.
    10221025      </p>
    10231026      <div id="rfc.iref.i.3"></div>
  • 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.