Achieve RFC 9112 HTTP/1.1 Request Syntax
Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2
Requirement levels: Applicable parsing and rejection rules include MUST and SHOULD obligations.
Achieve receives HTTP/1.1 requests after Node's llhttp parser has recognized the request line and field section. Achieve then validates the request-target form and HTTP/1.1 Host information visible through Node's request object.
Applicable requirements
- The request line has method, one space, request target, one space, and HTTP version before fields are parsed (RFC 9112 §3).
- SHOULD: A server normally responds 400 to an invalid request line unless it uses the narrowly permitted encoded-target redirect.
- MUST: Whitespace lines between the request line and first field are rejected or consumed and ignored; a server should ignore at least one leading empty line (§2.2 and §2.3).
- MUST: HTTP/1.1 requests contain one valid Host field where required by §3.2.
- MUST: A request target longer than the server accepts receives 414, not a header-size response.
Parser and Achieve checks
llhttp rejects malformed method tokens, versions, field syntax, conflicting message lengths, and parser overflow before routing. Achieve separately rejects fragments, malformed percent escapes, invalid target forms, missing or duplicate Host, invalid Host values, and authority inconsistencies. Valid origin-form, absolute-form, OPTIONS asterisk-form, and CONNECT authority-form controls are covered by tests.
Known request-target limitation
Node.js 24.22.2 reports both an oversized request target and oversized fields through its shared header-overflow boundary. The supported endpoint therefore returns 431 for a sufficiently long request target, while RFC 9112 §3 requires 414. Achieve cannot distinguish those conditions through the documented parser error exposed by Node without adding a second parser.
Responsibility and verification
Node/llhttp owns byte-level parsing; Achieve owns the post-parse target and authority checks it performs. Raw TCP probes cover valid controls, malformed lines, whitespace, Host, target forms, boundaries, and connection behavior. See the request-target investigation.
