FA-26833 / HTTP ranges / Member archive
Preamble bytes before the first delimiter do not form a range part · case 03
Preamble bytes before the first delimiter do not form a range part.
Case contract
Return only explicitly parsed part bodies; preamble is ignored even when nonempty.
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-preamble-not-part fixture 0 | ["bannerbannerbanner", "p"] | ["p"] | 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 ↗