- From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- Date: 2017年11月13日 19:49:14 +0200 (EET)
- To: Patrick McManus <mcmanus@ducksong.com>
- CC: HTTP working group mailing list <ietf-http-wg@w3.org>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>, hybi <hybi@ietf.org>
- Message-Id: <20171113174910.59FBC5DEB0@welho-filter3.welho.com>
5. Using Extended CONNECT To Bootstrap The WebSocket Protocol https://tools.ietf.org/html/draft-mcmanus-httpbis-h2-websockets-02#section-5 This should mention that :status = 200 replaces status code 101 used on RFC 6455, section 1.3. 1.3. Opening Handshake https://tools.ietf.org/html/rfc6455#section-1.3 " The handshake from the server is much simpler than the client " handshake. The first line is an HTTP Status-Line, with the status " code 101: " " HTTP/1.1 101 Switching Protocols " " Any status code other than 101 indicates that the WebSocket handshake " has not completed and that the semantics of HTTP still apply. The " headers follow the status code. 8.1.1. Upgrading from HTTP/2 https://tools.ietf.org/html/rfc7540#section-8.3 " HTTP/2 removes support for the 101 (Switching Protocols) " informational status code ([RFC7231], Section 6.2.2). " " The semantics of 101 (Switching Protocols) aren't applicable to a " multiplexed protocol. Alternative protocols are able to use the same " mechanisms that HTTP/2 uses to negotiate their use (see Section 3). / Kari Hurtta
Received on Monday, 13 November 2017 17:49:38 UTC