The origin allowlist conformance table, and the cross-backend suite that
runs it against each backend over the wire.
origin_conformance.json (beside this module) is the one statement of the
allowlist grammar and matcher, and of the host gate's check over them, both
spines implement. It holds three tables:
- parse rows —
{raw, ok: true} or {raw, errors: [{index?, kind}]}:
an allowlist value (as FUZ_ALLOWED_ORIGINS would carry it) and whether
it parses, or every refusal with its 1-based entry position (absent for a
list-level refusal) and its AllowedOriginsErrorKind. - match rows —
{patterns, origin, allowed}: a valid allowlist, one
Origin value (null for none), and the request-level answer. - host rows —
{patterns, hosts, allowed}: a valid allowlist, the
request's Host values ([] for none), and the host gate's answer.
A row may carry a note for the reader. The TS unit test reads the table
directly; describe_origin_conformance_cross_tests sends every row to a
backend's _testing_origin_check action and compares the answer, so the
Rust spine is held to the same rows without reading this file. A row whose
input holds U+0000 can't reach the action: the dispatcher refuses NUL in
params (params_nul) before any handler, and that refusal is what the
suite asserts for it. Its verdict is pinned by the TS unit test and by
fuz_http's own host and origin tests.