Changeset 1512

Jan 25, 2012, 10:58:38 AM (7 years ago)

Add payload to 426 response example (resolves #333)

2 edited


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

    r1510 r1512  
    358358  }
    359359  @bottom-center {
    360        content: "Expires July 27, 2012";
     360       content: "Expires July 28, 2012";
    361361  }
    362362  @bottom-right {
    410410      <meta name="dct.creator" content="Reschke, J. F.">
    411411      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    412       <meta name="dct.issued" scheme="ISO8601" content="2012-01-24">
     412      <meta name="dct.issued" scheme="ISO8601" content="2012-01-25">
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    414414      <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.">
    441441            </tr>
    442442            <tr>
    443                <td class="left">Expires: July 27, 2012</td>
     443               <td class="left">Expires: July 28, 2012</td>
    444444               <td class="right">HP</td>
    445445            </tr>
    494494            <tr>
    495495               <td class="left"></td>
    496                <td class="right">January 24, 2012</td>
     496               <td class="right">January 25, 2012</td>
    497497            </tr>
    498498         </tbody>
    524524         in progress”.
    525525      </p>
    526       <p>This Internet-Draft will expire on July 27, 2012.</p>
     526      <p>This Internet-Draft will expire on July 28, 2012.</p>
    527527      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    528528      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    20442044      </p>
    20452045      <div id="rfc.figure.u.8"></div>
    2046       <p>Example:</p>  <pre class="text2">HTTP/1.1 426 Upgrade Required
    2047 Upgrade: HTTP/2.0
     2046      <p>Example:</p>  <pre class="text">HTTP/1.1 426 Upgrade Required
     2047Upgrade: HTTP/3.0
    20482048Connection: Upgrade
    2050 </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
     2049Content-Length: 53
     2050Content-Type: text/plain
     2052<span id="s426body">This service requires use of the HTTP/3.0 protocol.
     2053</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
    20512054         alternative courses which may be available to the user.
    20522055      </p>
    34323435      </ul>
    34333436      <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>
    3434       <p id="rfc.section.C.20.p.1">None yet.</p>
     3437      <p id="rfc.section.C.20.p.1">Closed issues: </p>
     3438      <ul>
     3439         <li> &lt;<a href=""></a>&gt;: "example for 426 response should have a payload"
     3440         </li>
     3441      </ul>
    34353442      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    34363443      <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

    r1510 r1512  
    2225 <artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
     2225<artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
    22262226HTTP/1.1 426 Upgrade Required
    2227 Upgrade: HTTP/2.0
     2227Upgrade: HTTP/3.0
    22282228Connection: Upgrade
    2230 </artwork></figure>
     2229Content-Length: <x:length-of target="s426body"/>
     2230Content-Type: text/plain
     2232<x:span anchor="s426body">This service requires use of the HTTP/3.0 protocol.
    22322235   The server &SHOULD; include a message body in the 426 response which
    47514754<section title="Since draft-ietf-httpbis-p2-semantics-18" anchor="changes.since.18">
    4753   None yet.
     4756  Closed issues:
     4757  <list style="symbols">
     4758    <t>
     4759      <eref target=""/>:
     4760      "example for 426 response should have a payload"
     4761    </t>
     4762  </list>
Note: See TracChangeset for help on using the changeset viewer.