If-Range HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

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.

Exact message you may see resume download restarts from the beginningdownload resume not working ETag changesIf-Range header mismatchcurl: (33) HTTP server doesn't seem to support byte ranges
Seen on: HTTP cURL

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

  1. Publish new files under a new name
  2. Make ETags consistent across servers
  3. Don't modify the file in place

Detailed fix by platform

cURL

  1. curl -C - -O https://example.com/big.iso # resume

How to diagnose

  1. File — Unchanged?
  2. ETag — Same on all nodes?
  3. 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:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

102 — HTTP 102 Processing (HTTP)102201 — HTTP 201 Created (HTTP)201206 — HTTP 206 Partial Content (HTTP)206412 — HTTP 412 Precondition Failed (HTTP)412Accept-Ranges — HTML5 video can't seek or won't play: missing Accept-Ranges / wrong Content-Type (HTTP)Accept-RangesETag — Conditional requests always return 200 (ETag/Last-Modified never matches) (HTTP)ETagRange — Range request ignored: server returns 200 instead of 206 Partial Content (HTTP)RangeIf-Range

Explore the map of this error Full error map →

🧠 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.