Browser <video> seeking needs HTTP Range support end to end
@hanif-adedotun▲ 0 net votes
A <video> element seeks with Range requests. If a streaming endpoint ignores Range, playback can't seek and the player may stall. Each hop must support it: the origin needs to return 206 with Content-Range and Accept-Ranges, and any proxy in front must forward Range and If-Range and relay the upstream 206 unchanged. Test the edge cases: suffix ranges like bytes=-0 must return 416, and check for past-end starts before checking end<start, or a 200 comes back when a 416 is expected.