Websocket protocol Abstract



This series is the Chinese translation of rfc6455 websocket protocol. The original intention of translating related document specifications is to have a deeper understanding of websocket and related content.

This paper is mainly about websocket protocol

  • abstract

The specific content of the article is less, and the relevant chapters will be updated in succession. Students who are interested in it can continue to pay attention to it.

The translation version contains the understanding of some individuals, most of which are literal translation, while other parts may be free translation, which is suitable for students interested in understanding and learning. If you want to have a specific understanding of the whole websocket protocol, it is recommended to read it in English. If there are translation errors, you are welcome to point out.

PS: the blog stopped for another week due to the operation of hand fracture. Currently discharged, weekly update frequency will be restored.


Websocket protocol can communicate with remote host based on untrusted code through client running untrusted code in controlled environment. The security model for websocket is the origin based security model used by reusable web browsers (see here). This protocol consists of an open handshake process, followed by the basic data frame based on TCP. The goal of this technology is to provide a two-way traffic mechanism between browser based applications and the server without multiple HTTP connections (such as using XMLHttpRequest or iframe to simulate long polling).

Memo status

This is an Internet standard tracking document.

This document is produced by Internet Engineering Task Force (IETF). It represents the consensus of the Internet Engineering Task Force community. This document has been consulted by the public and the Internet Engineering Steering Group (iesg) has agreed to release it. More information on Internet standards can be found in Section II of RFC 5741.

Information and errata about the current status of this document, and how to provide feedback, can be found here.

Copyright notice

A person authorized to grant IETF credit in 2011 and considered to be the author of the document. All rights reserved.

This document is applicable to BCP 78 and related IETF documents before IETF, which are effective on this document release date. Please read these documents carefully. They explain your rights and restrictions on this document. The code components extracted from this document must contain simplified BSD license text as required by law as described in section IV.