RFC 8673: HTTP Random Access and Live Content
In plain English — editorial summary, not part of the RFC
To accommodate byte-range requests for content that has data appended over time, this document defines semantics that allow an HTTP client and a server to perform byte-range GET and HEAD requests that start at an arbitrary byte offset within the representation and end at an indeterminate offset.
Document record
- Document ID
- RFC8673
- Published
- November 2019
- Authors
- C. Pratt; D. Thakore; B. Stark
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8740Using TLS 1.3 with HTTP/2Obsoleted
February 2020
- RFC 88030-RTT TCP Convert ProtocolCurrent
July 2020
- RFC 8470Using Early Data in HTTPCurrent
September 2018
- RFC 8336The ORIGIN HTTP/2 FrameCurrent
March 2018
- RFC 9110HTTP SemanticsCurrent
June 2022
- RFC 9111HTTP CachingCurrent
June 2022
- RFC 9112HTTP/1.1Updated
June 2022
- RFC 9113HTTP/2Current
June 2022
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?