Changeset 2318

Timestamp:

28/07/13 10:28:18 (7 years ago)

Author:

julian.reschke@…

Message:

rephrase HEAD response payload header field requirement (see #451)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (2 diffs)
• p2-semantics.xml (modified) (2 diffs)

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

@@ -1410 +1410 @@
       <h3 id="rfc.section.4.3.2"><a href="#rfc.section.4.3.2">4.3.2</a>&nbsp;<a id="HEAD" href="#HEAD">HEAD</a></h3>
       <div id="rfc.iref.h.1"></div>
-      <p id="rfc.section.4.3.2.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> send a message body in the response (i.e., the response terminates at the end of the header block). Aside from the payload
-         header fields (<a href="#payload" title="Payload Semantics">Section&nbsp;3.3</a>), the server <em class="bcp14">SHOULD</em> send the same header fields in response to a HEAD request as it would have sent if the request had been a GET. This method
-         can be used for obtaining metadata about the selected representation without transferring the representation data. This method
-         is often used for testing hypertext links for validity, accessibility, and recent modification.
+      <p id="rfc.section.4.3.2.p.1">The HEAD method is identical to GET except that the server <em class="bcp14">MUST NOT</em> send a message body in the response (i.e., the response terminates at the end of the header block). The server <em class="bcp14">SHOULD</em> send the same header fields in response to a HEAD request as it would have sent if the request had been a GET, except that
+         the payload header fields (<a href="#payload" title="Payload Semantics">Section&nbsp;3.3</a>) <em class="bcp14">MAY</em> be omitted. This method can be used for obtaining metadata about the selected representation without transferring the representation
+         data and is often used for testing hypertext links for validity, accessibility, and recent modification.
       </p>
       <p id="rfc.section.4.3.2.p.2">A payload within a HEAD request message has no defined semantics; sending a payload body on a HEAD request might cause some
@@ -4526 +4525 @@
       <ul>
          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/303">http://tools.ietf.org/wg/httpbis/trac/ticket/303</a>&gt;: "400 response isn't generic"
+         </li>
+         <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/451">http://tools.ietf.org/wg/httpbis/trac/ticket/451</a>&gt;: "Content-Length in HEAD responses"
          </li>
       </ul>

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

@@ -1314 +1314 @@
    The HEAD method is identical to GET except that the server &MUST-NOT;
    send a message body in the response (i.e., the response terminates at the
-   end of the header block). Aside from the payload header fields
-   (<xref target="payload"/>), the server &SHOULD; send the same header fields
+   end of the header block). The server &SHOULD; send the same header fields
    in response to a HEAD request as it would have sent if the request had been
-   a GET. This method can be used for obtaining metadata about the selected
-   representation without transferring the representation data. This method is
+   a GET, except that the payload header fields (<xref target="payload"/>)
+   &MAY; be omitted. This method can be used for obtaining metadata about the
+   selected representation without transferring the representation data and is
    often used for testing hypertext links for validity, accessibility, and
    recent modification.
@@ -6396 +6396 @@
       "400 response isn't generic"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/451"/>:
+      "Content-Length in HEAD responses"
+    </t>
   </list>
 </t>