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

Timestamp:

25/04/13 14:25:26 (10 years ago)

Author:

julian.reschke@…

Message:

augment considerations for new header fields

File:

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

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

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires October 21, 2013"; 
+       content: "Expires October 27, 2013"; 
   } 
   @bottom-right {
@@ -494 +494 @@
       <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="2013-04-19">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-04-25">
       <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.">
@@ -522 +522 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">April 19, 2013</td>
+               <td class="right">April 25, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: October 21, 2013</td>
+               <td class="left">Expires: October 27, 2013</td>
                <td class="right"></td>
             </tr>
@@ -553 +553 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on October 21, 2013.</p>
+      <p>This Internet-Draft will expire on October 27, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -3618 +3618 @@
          </li>
          <li>
+            <p>Whether the field should be stored by origin servers that understand it upon a PUT request.</p>
+         </li>
+         <li>
             <p>Whether the field semantics are further refined by the context, such as by existing request methods or status codes.</p>
          </li>
@@ -3628 +3631 @@
          </li>
          <li>
-            <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>).
+            <p>That when the header is used in requests and affects response selection (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), it ought to be listed in the <a href="#header.vary" class="smpl">Vary</a> response header field (<a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section&nbsp;7.1.4</a>).
             </p>
          </li>
@@ -3790 +3793 @@
                   <td class="left">http</td>
                   <td class="left">standard</td>
-                  <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section&nbsp;7.1.4</a> 
+                  <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.4" title="Vary">Section&nbsp;7.1.4</a> 
                   </td>
                </tr>
@@ -4720 +4723 @@
                         <li><em>Section 4.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">4.3.3</a></li>
                         <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">6.3.1</a>, <a href="#rfc.xref.Part6.13">6.3.4</a>, <a href="#rfc.xref.Part6.14">6.3.5</a>, <a href="#rfc.xref.Part6.15">6.4.1</a>, <a href="#rfc.xref.Part6.16">6.4.2</a>, <a href="#rfc.xref.Part6.17">6.5.4</a>, <a href="#rfc.xref.Part6.18">6.5.5</a>, <a href="#rfc.xref.Part6.19">6.5.9</a>, <a href="#rfc.xref.Part6.20">6.5.12</a>, <a href="#rfc.xref.Part6.21">6.6.2</a></li>
-                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.26">7.1.4</a></li>
+                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.26">7.1.4</a>, <a href="#rfc.xref.Part6.29">8.3.1</a></li>
                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">4.3.2</a></li>
                         <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">4.3.4</a>, <a href="#rfc.xref.Part6.7">4.3.5</a></li>
@@ -4851 +4854 @@
             </li>
             <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
-                  <li>Vary header field&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">3.4.1</a>, <a href="#rfc.xref.header.vary.2">7.1</a>, <a href="#rfc.iref.v.1"><b>7.1.4</b></a>, <a href="#rfc.xref.header.vary.3">8.3.2</a></li>
+                  <li>Vary header field&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">3.4.1</a>, <a href="#rfc.xref.header.vary.2">7.1</a>, <a href="#rfc.iref.v.1"><b>7.1.4</b></a>, <a href="#rfc.xref.header.vary.3">8.3.1</a>, <a href="#rfc.xref.header.vary.4">8.3.2</a></li>
                </ul>
             </li>