FA-26590 / HTTP ranges / Member archive
Errors after partial headers abort instead of injecting a second response · case 05
Errors after partial headers abort instead of injecting a second response.
Case contract
If failure occurs after headers, abort with empty body; before headers return error500. No failure continues body.
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 |
|---|---|---|---|
| stream-error-after-headers fixture 0 | ["error500", ""] | ["abort", ""] | 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 ↗