HTTP 206 Partial Content
The server returned only the byte range the client asked for with a Range header.
HTTP 206 Partial ContentHTTP/1.1 206 Partial Contentstatus 206 partial contentContent-Range: bytes 0-1023 Meaning
Normal for video seeking and resumable downloads. Problems appear when the server ignores Range and returns the full 200, when Content-Range is wrong, or when a CDN or proxy mishandles ranges. Check Accept-Ranges and Content-Range.
Common causes
- Client sent a Range header (video, download manager)
- Server/CDN mis-handles ranges
- Wrong Content-Range or Content-Length
- Cache storing a partial response as complete
- Resume on a changed file
⚡ Quick fix
- Check
Accept-Ranges: byteson the server - Compare
Content-Rangewith the file size - Purge partial copies from caches
Detailed fix by platform
cURL
curl -r 0-1023 -i https://example.com/video.mp4
How to diagnose
- Accept-Ranges — bytes?
- Content-Range — Correct?
- File — Unchanged?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026