Changeset 1512 for draft-ietf-httpbis

Timestamp:

25/01/12 18:58:38 (11 years ago)

Author:

julian.reschke@…

Message:

Add payload to 426 response example (resolves #333)

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -358 +358 @@
   } 
   @bottom-center {
-       content: "Expires July 27, 2012"; 
+       content: "Expires July 28, 2012"; 
   } 
   @bottom-right {
@@ -410 +410 @@
       <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-01-24">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-01-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. 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.">
@@ -441 +441 @@
             </tr>
             <tr>
-               <td class="left">Expires: July 27, 2012</td>
+               <td class="left">Expires: July 28, 2012</td>
                <td class="right">HP</td>
             </tr>
@@ -494 +494 @@
             <tr>
                <td class="left"></td>
-               <td class="right">January 24, 2012</td>
+               <td class="right">January 25, 2012</td>
             </tr>
          </tbody>
@@ -524 +524 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on July 27, 2012.</p>
+      <p>This Internet-Draft will expire on July 28, 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>
@@ -2044 +2044 @@
       </p>
       <div id="rfc.figure.u.8"></div> 
-      <p>Example:</p>  <pre class="text2">HTTP/1.1 426 Upgrade Required
-Upgrade: HTTP/2.0
+      <p>Example:</p>  <pre class="text">HTTP/1.1 426 Upgrade Required
+Upgrade: HTTP/3.0
 Connection: Upgrade
-
-</pre><p id="rfc.section.7.4.19.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any
+Content-Length: 53
+Content-Type: text/plain
+
+<span id="s426body">This service requires use of the HTTP/3.0 protocol.
+</span></pre><p id="rfc.section.7.4.19.p.3">The server <em class="bcp14">SHOULD</em> include a message body in the 426 response which indicates in human readable form the reason for the error and describes any
          alternative courses which may be available to the user.
       </p>
@@ -3432 +3435 @@
       </ul>
       <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p2-semantics-18</a></h2>
-      <p id="rfc.section.C.20.p.1">None yet.</p>
+      <p id="rfc.section.C.20.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/333">http://tools.ietf.org/wg/httpbis/trac/ticket/333</a>&gt;: "example for 426 response should have a payload"
+         </li>
+      </ul>
       <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
       <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <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.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> 

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

@@ -2223 +2223 @@
 <figure>
 <preamble>Example:</preamble>
-<artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
+<artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
 HTTP/1.1 426 Upgrade Required
-Upgrade: HTTP/2.0
+Upgrade: HTTP/3.0
 Connection: Upgrade
-
-</artwork></figure>
+Content-Length: <x:length-of target="s426body"/>
+Content-Type: text/plain
+
+<x:span anchor="s426body">This service requires use of the HTTP/3.0 protocol.
+</x:span></artwork></figure>
 <t>
    The server &SHOULD; include a message body in the 426 response which
@@ -4751 +4754 @@
 <section title="Since draft-ietf-httpbis-p2-semantics-18" anchor="changes.since.18">
 <t>
-  None yet.
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/333"/>:
+      "example for 426 response should have a payload"
+    </t>
+  </list>
 </t>
 </section>