Changeset 2165


Ignore:
Timestamp:
Jan 25, 2013, 7:26:27 AM (7 years ago)
Author:
julian.reschke@…
Message:

Clarify that an extension conditional header can put conditions on resources other than the target resource; elaborate on WebDAV "If" header field (see [2161] and #96)

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

Legend:

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

    r2164 r2165  
    10821082      <p id="rfc.section.5.p.4">The conditional request header fields defined by this specification are ignored for request methods that never involve the
    10831083         selection or modification of a <a href="p2-semantics.html#representations" class="smpl">selected representation</a> (e.g., CONNECT, OPTIONS, and TRACE). Other conditional request header fields, defined by extensions to HTTP, might place conditions
    1084          on the state of the target resource in general, such as how the If header field in WebDAV has been defined to make a request
    1085          conditional on the presence or absence of a lock (<a href="#RFC4918" id="rfc.xref.RFC4918.2"><cite title="HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)">[RFC4918]</cite></a>, <a href="http://tools.ietf.org/html/rfc4918#section-10.4">Section 10.4</a>).
     1084         on the state of the target resource in general, or on a group of resources. For instance, the If header field in WebDAV can
     1085         make a request conditional on various aspects (such as locks) of multiple resources (<a href="#RFC4918" id="rfc.xref.RFC4918.2"><cite title="HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)">[RFC4918]</cite></a>, <a href="http://tools.ietf.org/html/rfc4918#section-10.4">Section 10.4</a>).
    10861086      </p>
    10871087      <p id="rfc.section.5.p.5">When more than one conditional request header field is present in a request, the order in which the fields are evaluated becomes
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2164 r2165  
    984984   OPTIONS, and TRACE). Other conditional request header fields, defined by
    985985   extensions to HTTP, might place conditions on the state of the target
    986    resource in general, such as how the If header field in WebDAV has been
    987    defined to make a request conditional on the presence or absence of a lock
     986   resource in general, or on a group of resources. For instance, the If header
     987   field in WebDAV can make a request conditional on various aspects (such
     988   as locks) of multiple resources
    988989   (<xref target="RFC4918" x:fmt="," x:sec="10.4"/>).
    989990</t>
Note: See TracChangeset for help on using the changeset viewer.