- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 206 Partial Content
206 Partial Content
The response holds only the part of the file that the Range header asked for. It is how downloads resume and video players skip ahead.
- Class
- 2xx Successful. The request was received, understood and accepted.
- Defined in
- RFC 9110
What it looks like
HTTP/1.1 206 Partial Content Content-Range: bytes 1000-1999/50000 Content-Length: 1000
When a server sends it
When the request has a Range header and the server supports ranges. The Content-Range header of the response says which bytes are included and how long the whole file is. A request for several ranges at once gets a multipart response.
What to do with it
Clients ask for ranges on purpose, so this is the answer they expect. Check Content-Range before you join parts together. When you resume a download, send If-Range with the ETag you got earlier, so that you receive the whole file again if it changed in the meantime.
A server that ignores Range answers 200 with the complete file, and a client has to cope with that too. If you run the server: video in Safari, for one, doesn't play without support for ranges.
Not to be confused with
| 200 OK | The whole file, also when a range was asked for and the server doesn't do ranges. |
|---|---|
| 416 Range Not Satisfiable | The range that was asked for lies outside the file. |
All codes are on the list of HTTP status codes, which can be searched by number and by word.