HTTP status codes / 2xx — Success
The server returned only the requested byte range.
The answer to a Range request: video streaming, resumable downloads and download managers live on 206. The Content-Range header describes which slice you got.
curl -i -H "Range: bytes=0-99" https://httpbin.org/range/1024
Same request, no terminal: paste this into the cURL converter for native code, or straight into ReqPad on your phone.
If you expected a full file but got 206, your client sent a Range header — possibly left over from a retry mechanism.
The fastest way to pin down a 206 is to reproduce the exact request and inspect what actually went over the wire — status, headers, timing and body, without your app code in the way. That is what an API client is for; ReqPad does it from your phone, with every request saved to history.
200 OK · 201 Created · 202 Accepted · 203 Non-Authoritative Information · 204 No Content · 205 Reset Content — or the full reference.
Build the request, send it, read status + headers + timing — on your iPhone. Free to start.