Changeset 1071 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

30/10/10 17:00:59 (10 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/p1-messaging.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -3247 +3247 @@
    The "Upgrade" general-header field allows the client to specify what
    additional communication protocols it would like to use, if the server 
-   chooses to switch protocols. Additionally, the server &MUST; use the Upgrade
-   header field within a 101 (Switching Protocols) response to indicate which
-   protocol(s) are being switched to.
+   chooses to switch protocols. Servers can use it to indicate what protocols
+   they are willing to switch to.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/><iref primary="true" item="Grammar" subitem="Upgrade-v"/>
@@ -3294 +3293 @@
    protocol on a different connection. For that purpose, it is more
    appropriate to use a 3xx redirection response (&status-3xx;).
+</t>
+<t>
+   Servers &MUST; include the "Upgrade" header field in 101 (Switching
+   Protocols) responses to indicate which protocol(s) are being switched to,
+   and &MUST; include it in 426 (Upgrade Required) responses to indicate
+   acceptable protocols to upgrade to. Servers &MAY; include it in any other
+   response to indicate that they are willing to upgrade to one of the
+   specified protocols.
 </t>
 <t>
@@ -4893 +4900 @@
   (<xref target="header.connection"/>)
 </t>
+<t>
+  Define the semantics of the "Upgrade" header field in responses other than
+  101 (this was incorporated from <xref target="RFC2817"/>).
+  (<xref target="header.upgrade"/>)
+</t>
 </section>
 </section>
@@ -5694 +5706 @@
       "Is * usable as a request-uri for new methods?"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/240"/>:
+      "Migrate Upgrade details from RFC2817"
+    </t>
   </list>
 </t>