Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 7936,RFC 8307,RFC 8441

Authors:

I. Fette
A. Melnikov

Stream:

IETF

Source:

hybi (app)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6455

Discuss this RFC: Send questions or comments to the mailing listhybi@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6455

Abstract

The WebSocket Protocol enables two-way communication between a clientrunning untrusted code in a controlled environment to a remote hostthat has opted-in to communications from that code. The securitymodel used for this is the origin-based security model commonly usedby web browsers. The protocol consists of an opening handshakefollowed by basic message framing, layered over TCP. The goal ofthis technology is to provide a mechanism for browser-basedapplications that need two-way communication with servers that doesnot rely on opening multiple HTTP connections (e.g., usingXMLHttpRequest or <iframe>s and long polling). [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.