Resumed download restarts from zero (If-Range validator mismatch)
A download manager tries to resume, but the server sends the full file again because the validator no longer matches.
resume download restarts from the beginningdownload resume not working ETag changesIf-Range header mismatchcurl: (33) HTTP server doesn't seem to support byte ranges Meaning
If-Range carries the ETag or Last-Modified from the first request. If the file changed, or the ETag differs between servers, the server correctly (or wrongly) returns 200 with the whole body. Keep files immutable once published and use consistent ETags across servers.
Common causes
- File replaced during the download
- ETag differs between load-balanced servers
- Last-Modified changing on each build
- Weak ETag used with If-Range
- CDN returning a different object version
⚡ Quick fix
- Publish new files under a new name
- Make ETags consistent across servers
- Don't modify the file in place
Detailed fix by platform
cURL
curl -C - -O https://example.com/big.iso # resume
How to diagnose
- File — Unchanged?
- ETag — Same on all nodes?
- Response — 206 or 200?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
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