Ignore:
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:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1069 r1071  
    32473247   The "Upgrade" general-header field allows the client to specify what
    32483248   additional communication protocols it would like to use, if the server
    3249    chooses to switch protocols. Additionally, the server &MUST; use the Upgrade
    3250    header field within a 101 (Switching Protocols) response to indicate which
    3251    protocol(s) are being switched to.
     3249   chooses to switch protocols. Servers can use it to indicate what protocols
     3250   they are willing to switch to.
    32523251</t>
    32533252<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Upgrade"/><iref primary="true" item="Grammar" subitem="Upgrade-v"/>
     
    32943293   protocol on a different connection. For that purpose, it is more
    32953294   appropriate to use a 3xx redirection response (&status-3xx;).
     3295</t>
     3296<t>
     3297   Servers &MUST; include the "Upgrade" header field in 101 (Switching
     3298   Protocols) responses to indicate which protocol(s) are being switched to,
     3299   and &MUST; include it in 426 (Upgrade Required) responses to indicate
     3300   acceptable protocols to upgrade to. Servers &MAY; include it in any other
     3301   response to indicate that they are willing to upgrade to one of the
     3302   specified protocols.
    32963303</t>
    32973304<t>
     
    48934900  (<xref target="header.connection"/>)
    48944901</t>
     4902<t>
     4903  Define the semantics of the "Upgrade" header field in responses other than
     4904  101 (this was incorporated from <xref target="RFC2817"/>).
     4905  (<xref target="header.upgrade"/>)
     4906</t>
    48954907</section>
    48964908</section>
     
    56945706      "Is * usable as a request-uri for new methods?"
    56955707    </t>
     5708    <t>
     5709      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/240"/>:
     5710      "Migrate Upgrade details from RFC2817"
     5711    </t>
    56965712  </list>
    56975713</t>
Note: See TracChangeset for help on using the changeset viewer.