Chunked transfer encoding - Wikipedia
Chunked transfer encoding is a streaming data transfer mechanism available in Hypertext Transfer Protocol (HTTP) version 1.1, defined in RFC 9112 §7.1. In chunked transfer encoding, the data stream is divided into a series of non-overlapping "chunks". The chunks are sent out and received independently of one another. No knowledge of the data stream outside the currently-being-processed chunk is necessary for both the sender and the receiver at any given time. Each chunk is preceded by its size in bytes. The transmission ends when a zero-length chunk is received. The chunked keyword in the Transfer-Encoding header is used to indicate chunked transfer. Chunked transfer encoding is not supported in HTTP/2, which provides its own mechanisms for data streaming.[1] The introduction of chunked encoding provided various benefits: For version 1.1 of the HTTP protocol, the chunked transfer mechanism is considered to be always and anyway acceptable, even if not listed in the TE (transfer encoding
Chunked transfer encoding - Wikipedia Jump to content From Wikipedia, the free encyclopedia Streaming data transfer mechanism in HTTP/1.1 This article needs more citations . Please help improve this article by adding citations to reliable sources . Unsourced material may be challenged and removed . Find sources: "Chunked transfer encoding" – news · newspapers · books · scholar · JSTOR ( June 2014 ) ( Learn how and when to remove this message ) Chunked transfer encoding is a streaming data transfer mechanism available in Hypertext Transfer Protocol (HTTP) version 1.1, defined in RFC 9112 §7.1 .
Explore this link on the map →related reading
- Transfer-Encoding header - HTTP | MDNdeveloper.mozilla.org
- H-Nets - the Past | Goomba Labgoombalab.github.io
- Why your website should be under 14kB in size | endtimes.devendtimes.dev
- The weirdly obscure art of Streamed HTML - DEV Communitydev.to
- Streaming HTML – Master.dev Blogfrontendmasters.com
- Variable-length encoding - Wikipediaen.wikipedia.org
- Server Sent Events are still not production ready after a decade. A lesson for me, a warning for you! - DEV Communitydev.to
- ByteByteGo | Technical Interview Prepbytebytego.com
- Image formats: Pixel data from encoders to decodersdeveloper.mozilla.org
- EIP-4844: Shard Blob Transactionseips.ethereum.org
- What should transferSize, encodedBodySize and decodedBodySize in Navigation + Resource Timing represent for responses where a Service Worker is involved? · Issue #124 · w3c/navigation-timing · GitHubgithub.com
- RFC 3550 - RTP: A Transport Protocol for Real-Time Applicationsdatatracker.ietf.org