RFC 6202: Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
In plain English — editorial summary, not part of the RFC
On today's Internet, the Hypertext Transfer Protocol (HTTP) is often used (some would say abused) to enable asynchronous, "server- initiated" communication from a server to a client as well as communication from a client to a server. This document describes known issues and best practices related to such "bidirectional HTTP" applications, focusing on the two most common mechanisms: HTTP long polling and HTTP streaming. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6202
- Published
- April 2011
- Authors
- S. Loreto; P. Saint-Andre; S. Salsano; G. Wilkins
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6249Metalink/HTTP: Mirrors and HashesCurrent
June 2011
- RFC 6331Moving DIGEST-MD5 to HistoricCurrent
July 2011
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 5843Additional Hash Algorithms for HTTP Instance DigestsCurrent
April 2010
- RFC 6585Additional HTTP Status CodesCurrent
April 2012
- RFC 5789PATCH Method for HTTPCurrent
March 2010
- RFC 7231Hypertext Transfer Protocol (HTTP/1.1): Semantics and ContentObsoleted
June 2014
- RFC 7232Hypertext Transfer Protocol (HTTP/1.1): Conditional RequestsObsoleted
June 2014
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?