Changeset 1512 for draft-ietf-httpbis
- Timestamp:
- 25/01/12 18:58:38 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1510 r1512 358 358 } 359 359 @bottom-center { 360 content: "Expires July 2 7, 2012";360 content: "Expires July 28, 2012"; 361 361 } 362 362 @bottom-right { … … 410 410 <meta name="dct.creator" content="Reschke, J. F."> 411 411 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 412 <meta name="dct.issued" scheme="ISO8601" content="2012-01-2 4">412 <meta name="dct.issued" scheme="ISO8601" content="2012-01-25"> 413 413 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 414 414 <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 "HTTP/1.1" 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> 442 442 <tr> 443 <td class="left">Expires: July 2 7, 2012</td>443 <td class="left">Expires: July 28, 2012</td> 444 444 <td class="right">HP</td> 445 445 </tr> … … 494 494 <tr> 495 495 <td class="left"></td> 496 <td class="right">January 2 4, 2012</td>496 <td class="right">January 25, 2012</td> 497 497 </tr> 498 498 </tbody> … … 524 524 in progress”. 525 525 </p> 526 <p>This Internet-Draft will expire on July 2 7, 2012.</p>526 <p>This Internet-Draft will expire on July 28, 2012.</p> 527 527 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 528 528 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2044 2044 </p> 2045 2045 <div id="rfc.figure.u.8"></div> 2046 <p>Example:</p> <pre class="text 2">HTTP/1.1 426 Upgrade Required2047 Upgrade: HTTP/ 2.02046 <p>Example:</p> <pre class="text">HTTP/1.1 426 Upgrade Required 2047 Upgrade: HTTP/3.0 2048 2048 Connection: Upgrade 2049 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 2049 Content-Length: 53 2050 Content-Type: text/plain 2051 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 2051 2054 alternative courses which may be available to the user. 2052 2055 </p> … … 3432 3435 </ul> 3433 3436 <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a> <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> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/333">http://tools.ietf.org/wg/httpbis/trac/ticket/333</a>>: "example for 426 response should have a payload" 3440 </li> 3441 </ul> 3435 3442 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 3436 3443 <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 2223 2223 <figure> 2224 2224 <preamble>Example:</preamble> 2225 <artwork type="message/http; msgtype="re quest"" x:indent-with=" ">2225 <artwork type="message/http; msgtype="response"" x:indent-with=" "> 2226 2226 HTTP/1.1 426 Upgrade Required 2227 Upgrade: HTTP/ 2.02227 Upgrade: HTTP/3.0 2228 2228 Connection: Upgrade 2229 2230 </artwork></figure> 2229 Content-Length: <x:length-of target="s426body"/> 2230 Content-Type: text/plain 2231 2232 <x:span anchor="s426body">This service requires use of the HTTP/3.0 protocol. 2233 </x:span></artwork></figure> 2231 2234 <t> 2232 2235 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"> 4752 4755 <t> 4753 None yet. 4756 Closed issues: 4757 <list style="symbols"> 4758 <t> 4759 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/333"/>: 4760 "example for 426 response should have a payload" 4761 </t> 4762 </list> 4754 4763 </t> 4755 4764 </section>
Note: See TracChangeset
for help on using the changeset viewer.