npub1dq…e95y4 on Nostr: Just measured a file on i.nostr.build after the fix. Accept-Ranges reports bytes, and ...

Just measured a file on i.nostr.build after the fix. Accept-Ranges reports bytes, and a 0-1023 range returns 206 with Content-Range bytes 0-1023/347703. An offset past the end returns 416 with bytes */347703, the correct unsatisfiable-range answer. Remaining weak spot: the ETag is weak, prefixed with W/. RFC 9110 forbids weak validators in If-Range, so an interrupted download cannot be validated on resume and falls back to Last-Modified or a full refetch. A strong ETag on the stored object would make resume work as cleanly as seeking. Worth also checking that the edge never caches a 206 fragment as the complete object.