A 206 Response Can Be a Successful Request for Part of a File

Illustration of generic cables and devices arranged on a violet desk
AI-generated conceptual illustration, not a product photograph or software screenshot.

Partial Content sounds like a download has gone wrong, but HTTP status 206 can mean the server successfully supplied the specific portion the client requested. The request matters alongside the response.

Look for the range

The MDN reference for 206 explains range responses. For a single requested range, Content-Range identifies the portion returned. This is different from assuming the response body contains the entire resource.

In a practice inspection, write down the requested byte interval and the interval reported in the response. Keep the complete resource size separate from the number of bytes in this particular transfer.

Diagnose the actual symptom

A media player or download tool may legitimately use range requests. Seeing 206 alone does not establish that playback is broken or that the original file is incomplete.

If there is a problem, describe what the application failed to do and inspect the relevant sequence of requests. One successful partial response may be only part of that sequence. Keeping the requested scope visible turns a potentially alarming label into a precise statement about the data exchanged, without treating every non-200 status as an error.