[hybi] draft-mcmanus-httpbis-h2-websockets-02.txt, 5. Using Extended CONNECT To Bootstrap The WebSocket Protocol, status code

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Mon, 13 November 2017 17:49 UTC

Return-Path: <khurtta@welho.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CCF812946E for <hybi@ietfa.amsl.com>; Mon, 13 Nov 2017 09:49:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Smwoy6RF2UB for <hybi@ietfa.amsl.com>; Mon, 13 Nov 2017 09:49:13 -0800 (PST)
Received: from welho-filter3.welho.com (welho-filter3.welho.com [83.102.41.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 493CF128768 for <hybi@ietf.org>; Mon, 13 Nov 2017 09:49:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by welho-filter3.welho.com (Postfix) with ESMTP id 59FBC5DEB0; Mon, 13 Nov 2017 19:49:10 +0200 (EET)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp1.welho.com ([IPv6:::ffff:83.102.41.84]) by localhost (welho-filter3.welho.com [::ffff:83.102.41.25]) (amavisd-new, port 10024) with ESMTP id jGK13MikIY7g; Mon, 13 Nov 2017 19:49:09 +0200 (EET)
Received: from hurtta09lk.keh.iki.fi (89-27-39-95.bb.dnainternet.fi [89.27.39.95]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by welho-smtp1.welho.com (Postfix) with ESMTPS id 8671E27F; Mon, 13 Nov 2017 19:49:04 +0200 (EET)
In-Reply-To: <CAOdDvNo8D6qsO5k-u-_Do2M142+ShSOVJTdzSKiNkw=8Z630_g@mail.gmail.com>
References: <CAOdDvNo8D6qsO5k-u-_Do2M142+ShSOVJTdzSKiNkw=8Z630_g@mail.gmail.com>
To: Patrick McManus <mcmanus@ducksong.com>
Date: Mon, 13 Nov 2017 19:49:14 +0200 (EET)
Sender: hurtta@hurtta09lk.keh.iki.fi
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: HTTP working group mailing list <ietf-http-wg@w3.org>, Kari Hurtta <hurtta-ietf@elmme-mailer.org>, hybi <hybi@ietf.org>
X-Mailer: ELM [version ME+ 2.5 PLalpha46+]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20171113174910.59FBC5DEB0@welho-filter3.welho.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/ulKeZdkFCyfBHnv70eRUgJl-f08>
Subject: [hybi] draft-mcmanus-httpbis-h2-websockets-02.txt, 5. Using Extended CONNECT To Bootstrap The WebSocket Protocol, status code
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Nov 2017 17:49:15 -0000

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