HTTP 206 Partial Content
Updated Free mock REST & WebSocket APIs
HTTP 206 Partial Content — The server is returning only the byte range the client asked for in its Range header.
- Class
- 2xx Success
- Defined in
- RFC 9110 §15.3.7
- Official
- Yes (IANA registry)
- Cacheable by default
- Yes (heuristically, per RFC 9110)
Try it: get a real 206 response
Our test endpoint answers every request with 206 Partial Content.
curl -i https://mockfox.dev/api/status/206Use it in tests, health-check monitors or to see how your client handles a 206. Add ?delay=2000 to slow it down.
What does HTTP 206 mean?
Powers resumable downloads and video seeking: the client sends Range: bytes=1000000- and the server returns 206 with Content-Range: bytes 1000000-4999999/5000000. Multiple ranges come back as multipart/byteranges. If the range is invalid the server answers 416 instead; if it ignores ranges it sends a normal 200 with the full body.
Handling 206
- Visitors: Nothing to fix — this is a success status.
- Developers: Make sure clients handle this status as success (
response.okis true for 200–299) and know whether to expect a body.
Example 206 response
HTTP/1.1 206 Partial Content
Content-Range: bytes 0-1023/4096
Content-Length: 1024
Content-Type: application/json
{"status":206,"error":"Partial Content"}2xx Success: The request was received, understood and accepted. See the full list of HTTP status codes.
Related status codes
- 200 OKThe request succeeded and the response contains the result.
- 416 Range Not SatisfiableThe byte range requested in the Range header is outside the size of the resource.
- 304 Not ModifiedThe cached copy the client already has is still valid, so no body is sent.
Related tools
Frequently asked questions
What does HTTP 206 Partial Content mean?
The server is returning only the byte range the client asked for in its Range header.
Is 206 an error?
No. 206 is a success status.
Where is 206 defined?
In RFC 9110 §15.3.7. It's listed in the IANA HTTP Status Code Registry.
How can I test how my app handles a 206?
Call https://mockfox.dev/api/status/206 — it responds with 206 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.