Coverage gap
RFC 9111 §3.4 (Combining Partial Content): a cache may combine multiple stored partial (206) responses for the same representation into a single, more complete response. No test actually stores two separate partials and then serves a combined/full body — the headline §3.4 behavior.
Currently tested
partial-store-partial-complete (tests/partial.mjs) stores one partial and checks the forwarded Range for the remainder, but never verifies the cache assembles the two pieces. (The suite even declares spec_anchors: ['combining.responses'] without exercising the combine.)
Suggested test
Request bytes 0–4 (store 206), then request bytes 5–9 (store 206). Then request the full representation (or a range spanning both) and assert the cache serves the combined body from its two stored partials without re-fetching.
Tag
[optimal] — RFC 9111 §3.4
Filed from an AI-assisted (Claude Code) coverage audit against RFC 9111/9110, under maintainer direction. Absence was grep-verified; the spec section number and MUST/SHOULD/optimal strength are from model knowledge, not re-read from the RFC text — worth confirming before writing the test.
Coverage gap
RFC 9111 §3.4 (Combining Partial Content): a cache may combine multiple stored partial (
206) responses for the same representation into a single, more complete response. No test actually stores two separate partials and then serves a combined/full body — the headline §3.4 behavior.Currently tested
partial-store-partial-complete(tests/partial.mjs) stores one partial and checks the forwarded Range for the remainder, but never verifies the cache assembles the two pieces. (The suite even declaresspec_anchors: ['combining.responses']without exercising the combine.)Suggested test
Request bytes 0–4 (store
206), then request bytes 5–9 (store206). Then request the full representation (or a range spanning both) and assert the cache serves the combined body from its two stored partials without re-fetching.Tag
[optimal] — RFC 9111 §3.4
Filed from an AI-assisted (Claude Code) coverage audit against RFC 9111/9110, under maintainer direction. Absence was grep-verified; the spec section number and MUST/SHOULD/optimal strength are from model knowledge, not re-read from the RFC text — worth confirming before writing the test.