Coverage gap
Multi-range requests / multipart/byteranges responses (RFC 9110 §14.4, §14.5) are untested — grep-verified: no multipart/byteranges anywhere. All range tests use single ranges.
Currently tested
tests/partial.mjs — single-range storage/serving only.
Suggested test
- Store/reuse a
206 carrying multipart/byteranges (multiple ranges in one response).
- A multi-range request served from a stored complete representation produces a correct
multipart/byteranges body.
Tag
[optimal] — RFC 9110 §14.4/§14.5
Filed from an AI-assisted (Claude Code) coverage audit against RFC 9111/9110, under maintainer direction. Absence was grep-verified; the spec section numbers and strength are from model knowledge, not re-read from the RFC text — worth confirming before writing the tests.
Coverage gap
Multi-range requests /
multipart/byterangesresponses (RFC 9110 §14.4, §14.5) are untested — grep-verified: nomultipart/byterangesanywhere. All range tests use single ranges.Currently tested
tests/partial.mjs— single-range storage/serving only.Suggested test
206carryingmultipart/byteranges(multiple ranges in one response).multipart/byterangesbody.Tag
[optimal] — RFC 9110 §14.4/§14.5
Filed from an AI-assisted (Claude Code) coverage audit against RFC 9111/9110, under maintainer direction. Absence was grep-verified; the spec section numbers and strength are from model knowledge, not re-read from the RFC text — worth confirming before writing the tests.