[billf]

Stack: #49 → #54 → #55 → #56.

Serves a single byte range for static assets, so audio and video can seek, with If-Range and 416 handling.

What this PR contains

• parseByteRange in src/mime/mime.ts parses one bytes= range in open-ended, bounded and suffix forms, clamped to the file size. Range unit names are case-insensitive (RFC 9110 §14.1). Multi-range and malformed headers are ignored, which RFC 9110 §14.2 allows. An inverted range is answered 416.
• ifRangeMatches: a Range applies only when If-Range is a strong match for the current ETag (RFC 9110 §13.1.5). Otherwise the full body is served.
• blobResponse answers 206 with Content-Range, 416 for an unsatisfiable range, and sends Accept-Ranges: bytes on full and partial responses.
• Range errors (416) are Cache-Control: no-store and keep the ETag and X-Content-Type-Options: nosniff. An out-of-bounds response for a hashed asset is never cached as immutable.
• The app-owned storage-URL route forwards a single Range to storage and passes 206 through. Multi-range headers are not forwarded. A storage 416 gets the same no-store policy.
• Tests: parser edge cases, If-Range, 416 caching, and component and app-owned Range responses.

Not in this PR

• In-memory blobs are still read whole and sliced. Stream component Range requests from storage instead of buffering files #55 streams component storage, and Stream inherited app-storage Range requests instead of loading the file #56 streams inherited app storage.

🤖 Generated with Claude Code

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/convex/static-hosting/@convex-dev/static-hosting@54

commit: e41a4e1

[billf]

This change is part of the following stack:

• Fix MIME types for audio, video and markdown #49
  • Serve single byte ranges with If-Range and 416 handling #54 ◀
    • Stream component Range requests from storage, resolved against file size #50
      • Stream inherited app-storage Range requests instead of loading the file #51

_{Change managed by git-spice.}