HTTP provides exactly one standardized feature for partial transfers, the Range request header. If the origin ignores Range, every GET starts at byte 0 and you cannot prevent the first N bytes from being sent again. A client-side workaround does not exist because the server decides what payload to stream.