Media Byte Ranges, Seeking, and Version Identity

Working case

Reviewer 47 jumps to minute 6 of a 391 MiB inspection recording. The browser requests bytes near a keyframe. The delivery service finds the exact immutable rendition and serves only the requested interval. During a background re-encode, a new rendition appears under a new identity rather than replacing the bytes being watched. The player can continue fetching ranges from the old rendition until its authorization or retention window ends. If the reviewer loses case permission, a later range request is denied even though earlier bytes were buffered. A signed delivery path, if used, is short-lived and bound to the case, rendition, and viewer policy.

Implementation boundary

function singleByteRange(start, end, total) {
  if (!Number.isInteger(start) || !Number.isInteger(end) || start < 0 || end < start || end >= total) return null;
  return { start, end, length: end - start + 1, total };
}
console.log(singleByteRange(4700, 4762, 391000000).length);
// Output: 63

Parse only the range forms the service intends to support; reject malformed or excessive multipart requests before allocating work. Resolve the file identity and length before interpreting a range. For a valid single interval, send the exact slice with matching partial status and range metadata; never claim a full response while sending a fragment. Keep one immutable rendition ID per encode, with a validator tied to those bytes. When a client resumes conditionally, a changed validator should cause a full coherent response or an explicit restart rather than mixed fragments. Enforce case access on every request or on a narrowly scoped delivery grant whose expiry and revocation behavior is documented. Test proxy and object-storage behavior, because an origin implementation can be correct while an intermediary strips or rewrites range metadata.

Cost and boundaries

Serving a requested interval of R bytes takes O(R) transfer and streaming work instead of O(B) for the full B-byte file. Parsing a bounded single range is O(1); unrestricted multipart ranges can amplify response assembly and should be capped. Frequent tiny seeks create request overhead, while very large read-ahead wastes bandwidth. Cacheable immutable renditions lower repeated origin reads but require a deliberate policy for private objects. A validator lookup and authorization check add latency to each range; design index and grant paths around measured load. Track partial-response correctness, seek-to-frame time, origin bytes, cache hits, rejected ranges, and permission revocations observed during playback.

Failure trace

Request the first 47 bytes, the last 63 bytes, and a range starting beyond the file length. Verify status, body length, and range metadata for each. Ask for a range with a stale validator after a new encode and ensure the response is coherent for one version. Change the asset while a proxy cache holds an old fragment; the rendition key must prevent mixed bytes. Revoke permission between two seeks and deny the second. Send a range list with thousands of spans and stop it before assembly. Confirm a browser can seek backward and forward through the actual deployed proxy, not only a local route handler.

Verification

Partial body and metadata agree on length.
A new encode has a new immutable identity.
Revocation is enforced on later range requests.

Practice drill

Publish a 391 MiB clip as rendition 29 and map the authorized case to it. Ask for bytes 4700 through 4762 and assert that exactly 63 bytes return, with a total length matching rendition 29. Publish rendition 30, then ask for the old interval with a stale conditional validator. Observe whether the client restarts or continues one immutable version. Revoke access, repeat the range, and inspect denial. Compare full-file transfer with the bytes needed for a seek-heavy reviewer session.

Decision note

A seek succeeds only when every partial response is authorized and belongs to one immutable asset revision.

Common Mistakes

Returning partial bytes with a full-response status.
Changing bytes behind a stable rendition URL.
Treating earlier buffer access as permanent permission.

Connected practice

Build Project: private inspection clip playback and review Web Development: media playback decisions quiz.