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/rfc7230.abdiff.txt

    r2654 r2655  
    864864
    865865
    866 Section 6.7., paragraph 9:
    867 OLD:
    868 
    869     The capabilities and nature of the application-level communication
    870     after the protocol change is entirely dependent upon the new
    871     protocol(s) chosen.  However, immediately after sending the 101
    872     response, the server is expected to continue responding to the
    873     original request as if it had received its equivalent within the new
    874     protocol (i.e., the server still has an outstanding request to
    875     satisfy after the protocol has been changed, and is expected to do so
    876     without requiring the request to be repeated).
    877 
    878 NEW:
    879 
    880     The capabilities and nature of the application-level communication
    881     after the protocol change is entirely dependent upon the new
    882     protocol(s) chosen.  However, immediately after sending the 101
    883     (Switching Protocols) response, the server is expected to continue
    884     responding to the original request as if it had received its
    885     equivalent within the new protocol (i.e., the server still has an
    886     outstanding request to satisfy after the protocol has been changed,
    887     and is expected to do so without requiring the request to be
    888     repeated).
    889 
    890 
    891866Section 7., paragraph 14:
    892867OLD:
Note: See TracChangeset for help on using the changeset viewer.