Achieve — High Level Logic Project. Creating a new meta design pattern.

Friendly in development. Fast in production. Just build your apps. Let Achieve do the rest.

← Back to technical specifications

Achieve RFC 9110 Range Requests and Partial Responses

Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2

Requirement levels: Range support is optional, but RFC 9110 imposes MUST, SHOULD, and SHOULD NOT requirements once a server processes a range request.

Achieve supports byte ranges for resources selected through its audiovisual MIME table. Range processing lets clients retrieve a useful portion of media while retaining validators and accurate representation length metadata.

Applicable requirements

Range selection

RFC 9110 §14.2 defines the Range field. Achieve accepts closed, open-ended, and suffix byte ranges. A satisfiable range produces one 206 Partial Content response with the selected bytes. A valid unsatisfiable range produces 416 Range Not Satisfiable and a Content-Range value containing the complete length. A malformed range is rejected with 400.

Achieve advertises byte support with Accept-Ranges: bytes. The 206 response carries the selected range in Content-Range and the exact partial byte count in Content-Length. HEAD performs the same representation selection but does not turn a media response into a partial response.

If-Range

RFC 9110 §13.1.5 makes If-Range conditional on a Range request. A matching strong entity tag permits range processing. A false condition causes the server to ignore Range and send the complete selected representation. A weak entity tag cannot satisfy If-Range.

Achieve treats date-form If-Range conservatively as false because its current resource model does not establish that a Last-Modified value is a sufficiently strong date validator under §8.8.2.2. This is permitted conservative behavior: exact textual equality with Last-Modified alone is not enough to establish strength.

Partial-response metadata

RFC 9110 §15.3.7 defines 206. For an ordinary single-part 206, Achieve supplies representation metadata including the content type and validator information. For a successful matching If-Range 206, the RFC says the sender SHOULD NOT repeat representation fields beyond the required set. Achieve omits Content-Type and Last-Modified in that case while retaining Date, ETag, Content-Range, partial Content-Length, Accept-Ranges, and Server.

The bytes and entity tag are unchanged by this field selection. A cache combining partial responses remains subject to RFC 9111 §3.4.

Automated verification

The byte-range verifier covers closed, open-ended, suffix, malformed, and unsatisfiable requests; ordinary 206 responses; matching and nonmatching If-Range entity tags; conservative date-form handling; exact bytes; 200/206/416 status selection; and response fields. The same cases run over HTTP, HTTPS, h2c, and secure HTTP/2. Conditional tests verify that ordinary preconditions are evaluated before range handling.

See Achieve HTTP conformance testing.

Limits

Achieve does not generate multipart/byteranges. When a request contains multiple members, it serves the first satisfiable range rather than a multipart response; multipart support is optional. Range serving applies to the audiovisual path, not every ordinary static resource. Date-form If-Range cannot currently produce a matching 206 because no strong date validator has been established.