Changeset 2386 for draft-ietf-httpbis/latest/p2-semantics.html

Timestamp:

13/09/13 12:35:27 (9 years ago)

Author:

julian.reschke@…

Message:

Note changes for [2380] (see #458 and #468)

File:

• draft-ietf-httpbis/latest/p2-semantics.html (modified) (3 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -4251 +4251 @@
          and the undesirable effect of potentially breaking relative links in content-negotiated resources. (<a href="#header.content-location" id="rfc.xref.header.content-location.5" title="Content-Location">Section&nbsp;3.1.4.2</a>)
       </p>
-      <p id="rfc.section.B.p.6">To be consistent with the method-neutral parsing algorithm of <a href="#Part1" id="rfc.xref.Part1.49"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, the definition of GET has been relaxed so that requests can have a body, even though a body has no meaning for GET (<a href="#GET" id="rfc.xref.GET.5" title="GET">Section&nbsp;4.3.1</a>).
-      </p>
-      <p id="rfc.section.B.p.7">Servers are no longer required to handle all Content-* header fields and use of <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> has been explicitly banned in PUT requests (<a href="#PUT" id="rfc.xref.PUT.4" title="PUT">Section&nbsp;4.3.4</a>).
+      <p id="rfc.section.B.p.6">To be consistent with the method-neutral parsing algorithm of <a href="#Part1" id="rfc.xref.Part1.49"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, the definition of GET has been relaxed so that requests can have a body, even though a body has no meaning for GET. (<a href="#GET" id="rfc.xref.GET.5" title="GET">Section&nbsp;4.3.1</a>)
+      </p>
+      <p id="rfc.section.B.p.7">Servers are no longer required to handle all Content-* header fields and use of <a href="p5-range.html#header.content-range" class="smpl">Content-Range</a> has been explicitly banned in PUT requests. (<a href="#PUT" id="rfc.xref.PUT.4" title="PUT">Section&nbsp;4.3.4</a>)
       </p>
       <p id="rfc.section.B.p.8">Definition of the CONNECT method has been moved from <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a> to this specification. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section&nbsp;4.3.6</a>)
@@ -4259 +4259 @@
       <p id="rfc.section.B.p.9">The <a href="#OPTIONS" class="smpl">OPTIONS</a> and <a href="#TRACE" class="smpl">TRACE</a> request methods have been defined as being safe. (<a href="#OPTIONS" id="rfc.xref.OPTIONS.4" title="OPTIONS">Section&nbsp;4.3.7</a> and <a href="#TRACE" id="rfc.xref.TRACE.4" title="TRACE">Section&nbsp;4.3.8</a>)
       </p>
-      <p id="rfc.section.B.p.10">The definition of the <a href="#header.expect" class="smpl">Expect</a> header field has been fixed to allow parameters for value-less expectations and simplified to allow trailing semicolons. (<a href="#header.expect" id="rfc.xref.header.expect.5" title="Expect">Section&nbsp;5.1.1</a>)
+      <p id="rfc.section.B.p.10">The <a href="#header.expect" class="smpl">Expect</a> header field's extension mechanism has been removed due to widely-deployed broken implementations. (<a href="#header.expect" id="rfc.xref.header.expect.5" title="Expect">Section&nbsp;5.1.1</a>)
       </p>
       <p id="rfc.section.B.p.11">The <a href="#header.max-forwards" class="smpl">Max-Forwards</a> header field has been restricted to the <a href="#OPTIONS" class="smpl">OPTIONS</a> and <a href="#TRACE" class="smpl">TRACE</a> methods; previously, extension methods could have used it as well. (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section&nbsp;5.1.2</a>)
@@ -4518 +4518 @@
          </li>
          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/452">http://tools.ietf.org/wg/httpbis/trac/ticket/452</a>&gt;: "Content-Length in HEAD responses"
+         </li>
+         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/458">http://tools.ietf.org/wg/httpbis/trac/ticket/458</a>&gt;: "Requirements upon proxies for Expect"
+         </li>
+         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/468">http://tools.ietf.org/wg/httpbis/trac/ticket/468</a>&gt;: "Expectation Extensions"
          </li>
          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/470">http://tools.ietf.org/wg/httpbis/trac/ticket/470</a>&gt;: "What is 'Cacheable'?"