Changeset 1071 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

Oct 30, 2010, 10:00:59 AM (9 years ago)

Author:

julian.reschke@…

Message:

From 2817: adopt Upgrade semantics for status != 101, plus status code 426 (see #240)

File:

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

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

@@ -612 +612 @@
      / "416"  ; &status-416;: Requested range not satisfiable
      / "417"  ; <xref target="status.417"/>: Expectation Failed
+     / "426"  ; <xref target="status.426"/>: Upgrade Required
      / "500"  ; <xref target="status.500"/>: Internal Server Error
      / "501"  ; <xref target="status.501"/>: Not Implemented
@@ -1952 +1953 @@
 </t>
 </section>
+
+<section title="426 Upgrade Required" anchor="status.426">
+  <iref primary="true" item="426 Upgrade Required (status code)" x:for-anchor=""/>
+  <iref primary="true" item="Status Codes" subitem="426 Upgrade Required" x:for-anchor=""/>
+<t>
+   The request can not be completed without a prior protocol upgrade. This
+   response &MUST; include an Upgrade header field (&header-upgrade;)
+   specifying the required protocols.
+</t>
+<figure>
+<preamble>Example:</preamble>
+<artwork type="message/http; msgtype=&#34;request&#34;" x:indent-with="  ">
+HTTP/1.1 426 Upgrade Required
+Upgrade: HTTP/2.0
+Connection: Upgrade
+
+</artwork></figure>
+<t>
+   The server &SHOULD; 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.
+</t>
+</section>
 </section>
 
@@ -2687 +2711 @@
    <c>
       <xref target="status.417"/>
+   </c>
+   <c>426</c>
+   <c>Upgrade Required</c>
+   <c>
+      <xref target="status.426"/>
    </c>
    <c>500</c>
@@ -3448 +3477 @@
 </t>
 <t>
+  Define status 426 (Upgrade Required) (this was incorporated from
+  <xref target="RFC2817"/>).
+  (<xref target="status.426"/>)
+</t>
+<t>
   Reclassify "Allow" as response header field, removing the option to
   specify it in a PUT request.
@@ -3546 +3580 @@
  "307" / "400" / "401" / "402" / "403" / "404" / "405" / "406" /
  "407" / "408" / "409" / "410" / "411" / "412" / "413" / "414" /
- "415" / "416" / "417" / "500" / "501" / "502" / "503" / "504" /
- "505" / extension-code
+ "415" / "416" / "417" / "426" / "500" / "501" / "502" / "503" /
+ "504" / "505" / extension-code
 
 <x:ref>TE</x:ref> = &lt;TE, defined in [Part1], Section 9.5&gt;
@@ -4005 +4039 @@
       "Migrate CONNECT from RFC2817 to p2"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/240"/>:
+      "Migrate Upgrade details from RFC2817"
+    </t>
   </list>
 </t>