Skip to content

Coverage gap: 416 / unsatisfiable range request handling #192

Description

@mnot

Coverage gap

No test covers a Range request the cache cannot satisfy from its stored representation, including the unsatisfiable case that yields 416 (Range Not Satisfiable) (RFC 9110 §15.5.17). Grep-verified: 416 appears nowhere in the suite.

Currently tested

partial-store-partial-complete (tests/partial.mjs) forwards for a missing tail, but there is no test for a Range that lies outside a stored partial's extent (forcing a forward) nor for an unsatisfiable Range.

Suggested test

  • Range outside the extent of a stored partial → cache forwards to origin.
  • Unsatisfiable Range (e.g. start beyond representation length) → 416 (from origin, passed through; or generated if the cache holds the complete representation).

Tag

[optimal] — RFC 9111 §3.4 / RFC 9110 §15.5.17


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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions