Everything about Byte serving
HTTP facility to fetch a specific part of a file
Byte serving is the process introduced in HTTP protocol 1.1 of sending only a portion of a message from a server to a client. Byte serving begins when an HTTP server advertises its willingness to serve partial requests using the Accept-Ranges response header. A client then requests a specific part of a file from the server using the Range request header. If the range is valid, the server sends it to the client with a 206 Partial Content status code and a Content-Range header listing the range sent. If the range is invalid, the server responds with a 416 Requested Range Not Satisfiable status code. Wikipedia →
🧠Start here: a 6-step reading path
- Read the overview: Byte servingA 5-minute orientation
- Pick up a classic book: A practical guide to testing wireless smartphone applicationsThe most-reprinted book on the subject
- Go sideways: HTTPA closely related topic
- Go sideways: Chunked transfer encodingA closely related topic
đź“– Definitions
No dictionary entry for this exact phrase.
🗂️ The subject at a glance
No outline available.
🏆 Landmark papers (most cited)
- No matching papers found.
đź“š Books worth reading
A practical guide to testing wireless smartphone applicationsJulian Harty · 2009- 📕The first-year experience cookbookRaymond Pun, Meggan Houlihan · 2017
Ranked by number of editions on Open Library, a rough measure of how lasting a book is.
đź”— Related topics
- HTTP HTTP (Hypertext Transfer Protocol) is an application layer protocol in the Internet protocol suite for distributed, collaborative, hypermedia information…
- Chunked transfer encoding Chunked transfer encoding is a streaming data transfer mechanism available in Hypertext Transfer Protocol (HTTP) version 1.1, defined in RFC 9112 §7.1…
- List of HTTP header fields This article lists standard and notable non-standard HTTP header fields. A core set of fields is standardized by the Internet Engineering Task Force (IETF)…
- List of HTTP status codes This article lists standard and notable non-standard HTTP response status codes. Standardized codes are defined by IETF as documented in Request for Comments…
- OBject EXchange OBEX (abbreviation of OBject EXchange, also termed IrOBEX) is a communication protocol that facilitates the exchange of binary objects between devices…
- HTTP ETag The ETag or entity tag is part of HTTP, the protocol for the World Wide Web. It is one of several mechanisms that HTTP provides for Web cache validation…
- Real-Time Messaging Protocol Real-Time Messaging Protocol (RTMP) is a communication protocol for streaming audio, video, and data over the Internet. Originally developed as a proprietary…
- Progressive download A progressive download is the transfer of digital media files from a server to a client, typically using the HTTP protocol when initiated from a computer…