Ignore:
Timestamp:
07/05/14 15:47:43 (6 years ago)
Author:
julian.reschke@…
Message:

expand a few status code mentions (#553)

File:
1 edited

Legend:

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

    r2654 r2655  
    23452345
    23462346</pre><p id="rfc.section.6.7.p.7">The capabilities and nature of the application-level communication after the protocol change is entirely dependent upon the
    2347                new protocol(s) chosen. However, immediately after sending the 101 response, the server is expected to continue responding
    2348                to the original request as if it had received its equivalent within the new protocol (i.e., the server still has an outstanding
    2349                request to satisfy after the protocol has been changed, and is expected to do so without requiring the request to be repeated).
     2347               new protocol(s) chosen. However, immediately after sending the <a href="p2-semantics.html#status.101" class="smpl">101 (Switching Protocols)</a> response, the server is expected to continue responding to the original request as if it had received its equivalent within
     2348               the new protocol (i.e., the server still has an outstanding request to satisfy after the protocol has been changed, and is
     2349               expected to do so without requiring the request to be repeated).
    23502350            </p>
    23512351            <p id="rfc.section.6.7.p.8">For example, if the Upgrade header field is received in a GET request and the server decides to switch protocols, it first
Note: See TracChangeset for help on using the changeset viewer.