The readers of the request headers the gates decide on — Origin (the
origin check), Origin and Referer (browser context), Host (the host
gate) and Content-Type (the CORS simple-request refusal) — as pure
functions over header lines.
One rule per reader, the Rust spine's fuz_http::request_headers reading
the same one, and the shared table
testing/cross_backend/request_header_conformance.json holding both to the
same rows. Each reader takes the header's lines — one field value per
header line, in the order sent, outer SP and HTAB already stripped
(get_header_lines of http/header_lines.ts on a request) — so a header
sent twice is something it can see.
A malformed Origin, Host or Content-Type — an empty line, more than
one line, a byte the grammar doesn't hold — reads refused, never
absent: reading a malformed browser signal as no signal at all would fail
open past the gate it feeds.
Join-invariance. A runtime without a per-line view (Bun, an in-process
app.request) hands the spine one line holding the repeated lines joined
with , . No origin, host or media type holds a comma, so each reader
refuses one anywhere in its value: the join of a repeat is then refused as
the repeat itself is, and every reading is the same over the lines and over
their join.
Hono-free: lines in, a reading out.