Changeset 1571 for draft-ietf-httpbis/latest/p3-payload.html

Timestamp:

09/03/12 09:35:34 (10 years ago)

Author:

fielding@…

Message:

#330 ETag and Last-Modified are metadata for the selected representation,
which is not always the same as the representation enclosed in the response.
Define those terms from p4 and use a separate table to referenve the fields.

File:

• draft-ietf-httpbis/latest/p3-payload.html (modified) (12 diffs)

draft-ietf-httpbis/latest/p3-payload.html

@@ -460 +460 @@
   } 
   @bottom-center {
-       content: "Expires September 9, 2012"; 
+       content: "Expires September 10, 2012"; 
   } 
   @bottom-right {
@@ -511 +511 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-03-08">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-03-09">
       <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. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
@@ -537 +537 @@
             </tr>
             <tr>
-               <td class="left">Expires: September 9, 2012</td>
+               <td class="left">Expires: September 10, 2012</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -594 +594 @@
             <tr>
                <td class="left"></td>
-               <td class="right">March 8, 2012</td>
+               <td class="right">March 9, 2012</td>
             </tr>
          </tbody>
@@ -622 +622 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on September 9, 2012.</p>
+      <p>This Internet-Draft will expire on September 10, 2012.</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>
@@ -764 +764 @@
          </li>
       </ul>
+      <p id="rfc.section.1.1.p.3"> <span id="rfc.iref.s.1"></span>  <dfn>selected representation</dfn>  
+      </p>
+      <ul class="empty">
+         <li>The current representation of the target resource that would have been selected in a successful response if the same request
+            had used the method GET and excluded any conditional request header fields.
+         </li>
+      </ul>
       <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="intro.conformance.and.error.handling" href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
       <p id="rfc.section.1.2.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
@@ -1018 +1025 @@
                   <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
                </tr>
+            </tbody>
+         </table>
+      </div>
+      <p id="rfc.section.4.1.p.3">Additional header fields define metadata about the selected representation, which might differ from the representation included
+         in the message for responses to some state-changing methods. The following header fields are defined as selected representation
+         metadata:
+      </p>
+      <div id="rfc.table.u.3">
+         <table class="tt full left" cellpadding="3" cellspacing="0">
+            <thead>
+               <tr>
+                  <th>Header Field Name</th>
+                  <th>Defined in...</th>
+               </tr>
+            </thead>
+            <tbody>
+               <tr>
+                  <td class="left">ETag</td>
+                  <td class="left"><a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
+               </tr>
                <tr>
                   <td class="left">Last-Modified</td>
-                  <td class="left"><a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.2</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
+                  <td class="left"><a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
                </tr>
             </tbody>
@@ -1196 +1223 @@
           text/html;level=2;q=0.4, */*;q=0.5
 </pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p>
-      <div id="rfc.table.u.3">
+      <div id="rfc.table.u.4">
          <table class="tt full left" cellpadding="3" cellspacing="0">
             <thead>
@@ -1411 +1438 @@
          server is informing recipients that this representation has its own, presumably more specific, identifier. For a GET or HEAD
          request, this is an indication that the effective request URI identifies a resource that is subject to content negotiation
-         and the representation selected for this response can also be found at the identified URI. For other methods, such a Content-Location
+         and the selected representation for this response can also be found at the identified URI. For other methods, such a Content-Location
          indicates that this representation contains a report on the action's status and the same report is available (for future access
          with GET) at the given URI. For example, a purchase transaction made via a POST request might include a receipt document as
@@ -2161 +2188 @@
       </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
-      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> 
+      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> 
       </p>
       <div class="print2col">
@@ -2270 +2297 @@
                      </ul>
                   </li>
-                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.1</a>, <a href="#Part4"><b>10.1</b></a><ul>
-                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.1</a></li>
+                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.1</a>, <a href="#rfc.xref.Part4.2">4.1</a>, <a href="#Part4"><b>10.1</b></a><ul>
+                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.2">4.1</a></li>
+                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">4.1</a></li>
                      </ul>
                   </li>
@@ -2343 +2371 @@
                </ul>
             </li>
+            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
+                  <li>selected representation&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>1.1</b></a></li>
+               </ul>
+            </li>
          </ul>
       </div>