FAILURE MAP
← Case archive

FA-6991 / Proxy forwarding / Open access

Max forwards is decremented only for trace and options · case 01

Max forwards is decremented only for trace and options.

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

ROOT CAUSE

The faulty implementation uses `max(0,count-1)` for the max-forwards-is-decremented-only-for-trace-and-options decision.

THE FAILURE

The faulty implementation uses `max(0,count-1)` for the max-forwards-is-decremented-only-for-trace-and-options decision.

Unsuccessful approach: The attempted repair uses `count` and still violates a separate fixture.

Case contract

Bounded offline decision model: max forwards is decremented only for trace and options. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic proxy forwarding model isolates the max-forwards-is-decremented-only-for-trace-and-options policy at a network component boundary.

1 / The failure

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json
import ipaddress
import re
from urllib.parse import urlsplit, urljoin
N = 1
observations = []
def solve(method, count):
    return max(0,count-1)
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
_fixtures = ["check('fixture 1', solve('GET', 5), 5)", "check('fixture 2', solve('OPTIONS', 5), 4)", "check('fixture 3', solve('TRACE', 0), 0)", "check('fixture 4', solve('POST', 0), 0)"]
for _line in _fixtures[N % len(_fixtures):] + _fixtures[:N % len(_fixtures)]:
    exec(_line)
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
fixture 244Passed
fixture 300Passed
fixture 400Passed
fixture 145Failed

SHA-256 / a691ebec55dfd755f79c80364ad77c30519199684f3ddebdc537fce5be0dfce8

2 / The unsuccessful fix

Exit 1
"""Failure Map reference implementation. Python standard library only."""
import json
import ipaddress
import re
from urllib.parse import urlsplit, urljoin
N = 1
observations = []
def solve(method, count):
    return count
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
_fixtures = ["check('fixture 1', solve('GET', 5), 5)", "check('fixture 2', solve('OPTIONS', 5), 4)", "check('fixture 3', solve('TRACE', 0), 0)", "check('fixture 4', solve('POST', 0), 0)"]
for _line in _fixtures[N % len(_fixtures):] + _fixtures[:N % len(_fixtures)]:
    exec(_line)
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
fixture 254Failed
fixture 300Passed
fixture 400Passed
fixture 155Passed

SHA-256 / 3e5076a1f56c0e6b6d666f33b45169c442c594be31e748db1a686b3af0acb1fb

HELD IN THE MEMBER ARCHIVE

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

This mechanism has 4 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

Bounded deterministic policy model over validated inputs; not a complete protocol stack or an interoperability claim. The five variants rotate the same explicit fixture set. 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:38:07.268029+00:00.

Case digest / e2d613703a34a4a21ff158cf557d194b18d11f7914239c2e790ace0a3707f080