Ignore:
Timestamp:
24/09/13 01:57:10 (8 years ago)
Author:
fielding@…
Message:

clarify that 100-continue needs to be answered with a 100 before any 101 and client needs to send entire request message before using the upgraded protocol

File:
1 edited

Legend:

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

    r2406 r2410  
    3535  <!ENTITY header-date            "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3636  <!ENTITY header-etag            "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     37  <!ENTITY header-expect          "<xref target='Part2' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3738  <!ENTITY header-expires         "<xref target='Part6' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    3839  <!ENTITY header-last-modified   "<xref target='Part4' x:rel='#header.last-modified' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    32863287   the listed protocols.  A server &MUST; ignore an Upgrade header field that
    32873288   is received in an HTTP/1.0 request.
     3289</t>
     3290<t>
     3291   A client cannot begin using an upgraded protocol on the connection until
     3292   it has completely sent the request message (i.e., the client can't change
     3293   the protocol it is sending in the middle of a message).
     3294   If a server receives both Upgrade and an <x:ref>Expect</x:ref> header field
     3295   with the "100-continue" expectation (&header-expect;), the
     3296   server &MUST; send a <x:ref>100 (Continue)</x:ref> response before sending
     3297   a <x:ref>101 (Switching Protocols)</x:ref> response.
    32883298</t>
    32893299<t>
Note: See TracChangeset for help on using the changeset viewer.