FA-7523 / Multiplexed protocols / Member archive

Http2 field names must be lowercase · case 03

Http2 field names must be lowercase.

Member previewVariant 3 · 3 implementations · 4 checks per implementation

Case contract

Bounded offline decision model: http2 field names must be lowercase. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic multiplexed protocols model isolates the http2-field-names-must-be-lowercase policy at a network component boundary.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 1	`true`	`false`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.