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

Timestamp:

Jul 5, 2012, 11:32:41 PM (7 years ago)

Author:

julian.reschke@…

Message:

Work-in-progress: hyperlink status codes definitions (P5)

File:

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

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

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires January 6, 2013"; 
+       content: "Expires January 7, 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-07-05">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-07-06">
       <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 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation.">
@@ -528 +528 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 6, 2013</td>
+               <td class="left">Expires: January 7, 2013</td>
                <td class="right">greenbytes</td>
             </tr>
             <tr>
                <td class="left"></td>
-               <td class="right">July 5, 2012</td>
+               <td class="right">July 6, 2012</td>
             </tr>
          </tbody>
@@ -563 +563 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on January 6, 2013.</p>
+      <p>This Internet-Draft will expire on January 7, 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>
@@ -2330 +2330 @@
       <p id="rfc.section.6.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation
          because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s)
-         of the representation (e.g., the 206 status code).
+         of the representation (e.g., the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code).
       </p>
       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2>
@@ -2391 +2391 @@
             target resource.
          </li>
-         <li>If the response status code is 204, 206, or 304 and the request method was GET or HEAD, the response payload is a partial
-            representation of the target resource.
+         <li>If the response status code is 204, <a href="p5-range.html#status.206" class="smpl">206</a>, or 304 and the request method was GET or HEAD, the response payload is a partial representation of the target resource.
          </li>
          <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload