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 9112 §3 Request Targets and RFC 9110 §7.2 Authority

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

Requirement levels: The applicable HTTP/1.1 and HTTP/2 rules include MUST and MUST NOT requirements for target forms, Host or authority information, and malformed input.

Achieve validates the target and authority information exposed by Node before it performs method dispatch or filesystem routing. This keeps malformed syntax, ambiguous authority, and application-path resolution separate concerns.

Applicable requirements

HTTP/1.1 target forms

RFC 9112 §3.2 defines origin-form, absolute-form, authority-form, and asterisk-form. Achieve accepts origin-form for ordinary requests and recognizes absolute-form HTTP or HTTPS targets, using their path and query for resource selection. Authority-form is valid only for CONNECT, while * is valid only with OPTIONS.

An HTTP/1.1 request must contain exactly one syntactically valid Host field. Achieve rejects missing, duplicate, or invalid Host values. Absolute-form authority is parsed independently; request processing still validates the Host information supplied by the client.

HTTP/2 authority

RFC 9113 §8.3.1 defines request pseudo-header fields. Node and nghttp2 validate the HTTP/2 field block. Achieve additionally requires authority information from :authority or host, validates each value, and requires the normalized values to agree when both are present. Normalization accounts for case, default ports, IPv6 notation, and safe percent-encoding equivalence.

From target to resource

After validation, Achieve passes the origin-form resource target into method dispatch. Query information is available for request input; the path is decoded and resolved inside the configured application space. A fragment is not valid in an HTTP request target. Invalid percent encodings, backslash path forms, unsuitable target forms, and authority conflicts are rejected before routing.

Runtime boundary and known limitation

Node's HTTP parser decides whether an HTTP/1.1 request line and field section can be parsed at all. RFC 9112 §3 says a server receiving a request-target longer than any URI it wishes to parse MUST respond with 414. Node 24.22.2 reports request-target and header-field overflow through the same parser condition and returns 431 for an excessive target. Standalone Node reproduces the result, and Achieve receives no parsed request to distinguish it. This remains a runtime-owned nonconformance of the complete endpoint.

Verification

Request-target, syntax, path, authority, CONNECT, OPTIONS, and HTTP/2 authority tests cover valid forms and rejection controls. Raw-TCP boundary probes distinguish long request targets from oversized fields and record actual status and connection closure. HTTP/2 frame probes cover pseudo-header ordering, duplication, malformed values, authority agreement, and stream-versus-connection error behavior.

See Achieve HTTP conformance testing and the assessment evidence index.

Limits

Achieve does not implement successful CONNECT tunnels. Its accepted public routes are origin-server paths, not a general forward-proxy interface. Parser failures that occur before Node constructs a request object can only be handled through the limited parser-error information exposed by the runtime.