Changeset 1912

Timestamp:

22/09/12 08:24:07 (10 years ago)

Author:

fielding@…

Message:

fix recently added intro text that incorrectly implied that a HEAD response's representation header fields would be the same as a 200 response for GET; they are the headers for any status code.

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p2-semantics.xml (modified) (1 diff)

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

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires March 25, 2013"; 
+       content: "Expires March 26, 2013"; 
   } 
   @bottom-right {
@@ -497 +497 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-09-21">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-09-22">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
@@ -528 +528 @@
             </tr>
             <tr>
-               <td class="left">Expires: March 25, 2013</td>
+               <td class="left">Expires: March 26, 2013</td>
                <td class="right">greenbytes</td>
             </tr>
             <tr>
                <td class="left"></td>
-               <td class="right">September 21, 2012</td>
+               <td class="right">September 22, 2012</td>
             </tr>
          </tbody>
@@ -560 +560 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on March 25, 2013.</p>
+      <p>This Internet-Draft will expire on March 26, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -884 +884 @@
       </p>
       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="representation.header.fields" href="#representation.header.fields">Representation Header Fields</a></h2>
-      <p id="rfc.section.3.1.p.1">Representation header fields define metadata about the representation data enclosed in the message body or, if no message
-         body is present, about the representation that would have been transferred in a <a href="#status.200" class="smpl">200 (OK)</a> response to a simultaneous GET request with the same effective request URI.
+      <p id="rfc.section.3.1.p.1">Representation header fields provide metadata about the representation. When a message includes a payload body, the representation
+         header fields describe how to interpret the representation data enclosed in the payload body. In a response to a HEAD request,
+         the representation header fields describe the representation data that would have been enclosed in the payload body if the
+         same request had been a GET.
       </p>
       <p id="rfc.section.3.1.p.2">The following header fields are defined as representation metadata:</p>

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

@@ -308 +308 @@
   <x:anchor-alias value="representation-header"/>
 <t>
-   Representation header fields define metadata about the representation data
-   enclosed in the message body or, if no message body is present, about
-   the representation that would have been transferred in a <x:ref>200 (OK)</x:ref>
-   response to a simultaneous GET request with the same effective request URI.
+   Representation header fields provide metadata about the representation.
+   When a message includes a payload body, the representation header fields
+   describe how to interpret the representation data enclosed in the payload
+   body.  In a response to a HEAD request, the representation header fields
+   describe the representation data that would have been enclosed in the
+   payload body if the same request had been a GET.
 </t>
 <t>