FA-26838 / HTTP ranges / Member archive
Range body whitespace remains byte-exact after framing removal · case 03
Range body whitespace remains byte-exact after framing removal.
Case contract
framed ends with exactly one framing CRLF. Return all preceding payload bytes; do not trim payload whitespace.
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 |
|---|---|---|---|
| multipart-client-body-not-strip fixture 0 | "ppp" | "ppp\r\n" | 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 ↗