Achieve RFC 9113 HTTP/2 Server Push
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: Server push itself is optional; mandatory rules apply if it is used or a server receives PUSH_PROMISE.
Achieve does not initiate HTTP/2 server push. It does not call Node's push-stream API, synthesize promised requests, or expose an Achieve push configuration.
Applicable requirements
- MUST NOT: A server must not push after the client disables push with
SETTINGS_ENABLE_PUSH=0(RFC 9113 §6.5.2). - MUST: A server receiving PUSH_PROMISE from a client treats it as connection
PROTOCOL_ERROR(§8.4). - If push is used, promised requests must be safe, cacheable, authoritative, and contain no content or trailers. Those conditional obligations are not activated by Achieve because it does not push.
Qualified behavior
Non-use means Achieve cannot exceed a peer's server-initiated stream limit or violate a client's disabled-push setting. On Node.js 24.22.2, a raw client PUSH_PROMISE receives the required connection PROTOCOL_ERROR, correcting the earlier Node 22 error-code result.
Feature status
Server push is an optional HTTP/2 capability, not a hidden Achieve feature. Applications receive ordinary client-initiated requests and produce their responses. This page does not imply support for preloading, pushed-response cache management, or application-created PUSH_PROMISE frames.
Verification
Source inspection confirms no push API call. Raw-frame qualification verifies client PUSH_PROMISE rejection and SETTINGS behavior. The result belongs primarily to Node/nghttp2; the decision not to originate push belongs to Achieve.
