metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 6455: The WebSocket Protocol

Still current, but amended. Parts of this document are changed or extended by RFC 7936, RFC 8307, RFC 8441. Read both.

In plain English — editorial summary, not part of the RFC

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. The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or <iframe>s and long polling). [STANDARDS-TRACK]

Document record

Document ID
RFC6455
Published
December 2011
Authors
I. Fette; A. Melnikov
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
71
Also known as
—
Updated by:
RFC 7936, RFC 8307, RFC 8441

Topics

Referenced by

3 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6455-the-websocket-protocol