FAILURE MAP
← Case archive

FA-26701 / HTTP ranges / Open access

Known complete length must extend beyond every returned endpoint · case 01

Known complete length must extend beyond every returned endpoint.

Verified by executionVariant 1 · 6 checks per implementationDownload source bundle ↓JSON ↗

ROOT CAUSE

The content-range-total-beyond-end decision uses return start>=0 and end>=start.

THE FAILURE

The content-range-total-beyond-end decision uses return start>=0 and end>=start.

Unsuccessful approach: The partial repair uses return start>=0 and end>=start and (total is None or total>=end), which still violates the stated contract.

Case contract

Return valid for nonnegative ordered endpoints and either unknown total or total strictly greater than end. No interval slicing is performed.

Why this case matters

Range responses combine representation identity, conditional requests, framing, and partial-object state.

1 / The failure

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(start, end, total):
    return start>=0 and end>=start
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('content-range-total-beyond-end fixture 0', solve(0,N,N), False)
check('content-range-total-beyond-end fixture 1', solve(0,N,N+1), True)
check('content-range-total-beyond-end fixture 2', solve(0,N,None), True)
check('content-range-total-beyond-end fixture 3', solve(N,0,N+1), False)
check('content-range-total-beyond-end fixture 4', solve(-1,N,N+1), False)
check('content-range-total-beyond-end fixture 5', solve(0,0,0), False)
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
Boundary fixtureActualExpectedOutcome
content-range-total-beyond-end fixture 0TrueFalseFailed
content-range-total-beyond-end fixture 1TrueTruePassed
content-range-total-beyond-end fixture 2TrueTruePassed
content-range-total-beyond-end fixture 3FalseFalsePassed
content-range-total-beyond-end fixture 4FalseFalsePassed
content-range-total-beyond-end fixture 5TrueFalseFailed

SHA-256 / 43db69197d8e13a3ceb8edca2449fb498d8112196fdd753f741e945b2bb6d17f

2 / The unsuccessful fix

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json

N = 1
observations = []
def solve(start, end, total):
    return start>=0 and end>=start and (total is None or total>=end)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('content-range-total-beyond-end fixture 0', solve(0,N,N), False)
check('content-range-total-beyond-end fixture 1', solve(0,N,N+1), True)
check('content-range-total-beyond-end fixture 2', solve(0,N,None), True)
check('content-range-total-beyond-end fixture 3', solve(N,0,N+1), False)
check('content-range-total-beyond-end fixture 4', solve(-1,N,N+1), False)
check('content-range-total-beyond-end fixture 5', solve(0,0,0), False)
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
Boundary fixtureActualExpectedOutcome
content-range-total-beyond-end fixture 0TrueFalseFailed
content-range-total-beyond-end fixture 1TrueTruePassed
content-range-total-beyond-end fixture 2TrueTruePassed
content-range-total-beyond-end fixture 3FalseFalsePassed
content-range-total-beyond-end fixture 4FalseFalsePassed
content-range-total-beyond-end fixture 5TrueFalseFailed

SHA-256 / e9bcf181284dc7911ea5d2cff6bba5f1d63becc264eae715dc16cd7f236be792

HELD IN THE MEMBER ARCHIVE

The verified repair and its recorded checks are member-only.

This mechanism has 6 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.

Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.

Member access is invitation-based. Sign in with your invited account to inspect the repair.

Sign in to the archive ↗

Verification & scope

Deterministic simplified range service, with stipulated local policies and already parsed trusted inputs; not a complete HTTP implementation. This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.

Observations recorded using Python 3.12.14 at 2026-09-29T14:41:18.317932+00:00.

Case digest / 045aeccb64fe1bf1d726b964a92fc920bebe01f34609d6af95bb164433306da8