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/auth48/p1-messaging.unpg.txt

    r2654 r2655  
    32223222   after the protocol change is entirely dependent upon the new
    32233223   protocol(s) chosen.  However, immediately after sending the 101
    3224    response, the server is expected to continue responding to the
    3225    original request as if it had received its equivalent within the new
    3226    protocol (i.e., the server still has an outstanding request to
    3227    satisfy after the protocol has been changed, and is expected to do so
    3228    without requiring the request to be repeated).
     3224   (Switching Protocols) response, the server is expected to continue
     3225   responding to the original request as if it had received its
     3226   equivalent within the new protocol (i.e., the server still has an
     3227   outstanding request to satisfy after the protocol has been changed,
     3228   and is expected to do so without requiring the request to be
     3229   repeated).
    32293230
    32303231   For example, if the Upgrade header field is received in a GET request
     
    32373238   unless the received message semantics can be honored by the new
    32383239   protocol; an OPTIONS request can be honored by any protocol.
    3239 
    32403240
    32413241
Note: See TracChangeset for help on using the changeset viewer.