FA-6905 / Content negotiation / Member archive

Charset name comparison is case insensitive · case 05

Charset name comparison is case insensitive.

Member previewVariant 5 · 3 implementations · 4 checks per implementation

Case contract

Bounded offline decision model: charset name comparison is case insensitive. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic content negotiation model isolates the charset-name-comparison-is-case-insensitive 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 2	`false`	`true`	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.