FA-26667 / HTTP ranges / Member archive
Only outer optional whitespace is accepted around range unit tokens · case 02
Only outer optional whitespace is accepted around range unit tokens.
Case contract
Trim spaces and tabs around unit; return bytes only for exact case-insensitive bytes token afterward, otherwise None. Interior whitespace is invalid.
Why this case matters
Range responses combine representation identity, conditional requests, framing, and partial-object state.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| range-unit-whitespace fixture 0 | "bytes" | null | 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.
Sign in to the archive ↗