Skip to main content

WebSocket over HTTP/2

Document Type Expired Internet-Draft (individual)
Author Yutaka Hirano
Last updated 2015-02-13 (Latest revision 2014-08-12)
Stream (None)
Intended RFC status (None)
Expired & archived
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


The WebSocket protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. Since it requires one TCP connection for every WebSocket connection, having multiple WebSocket connections between the same client and the same server is inefficient. On the other hand, HTTP/2 specifies a fast, secure, multiplexed framing protocol. This document provides bi- directional multiplexed communication by layering WebSocket on top of HTTP/2. Please send feedback to the mailing list.


Yutaka Hirano

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)