FAILURE MAP

Understand the failure.
Verify the repair.

Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.

Explore the cases ↓How results are verified ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

WHAT THE ARCHIVE CONTAINS

100840 executable cases. 20168 are open.

Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.

The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗

A RECORD OF WHAT WENT WRONG

Browse the archive / 100840

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-28001

Reject malformed redirect authorities without interpreting path text as an authority: network path host · case 01

Reject malformed redirect authorities without interpreting path text as an authority: the network path host branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28002

Reject malformed redirect authorities without interpreting path text as an authority: network path host · case 02

Reject malformed redirect authorities without interpreting path text as an authority: the network path host branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28003

Reject malformed redirect authorities without interpreting path text as an authority: network path host · case 03

Reject malformed redirect authorities without interpreting path text as an authority: the network path host branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28004

Reject malformed redirect authorities without interpreting path text as an authority: network path host · case 04

Reject malformed redirect authorities without interpreting path text as an authority: the network path host branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28005

Reject malformed redirect authorities without interpreting path text as an authority: network path host · case 05

Reject malformed redirect authorities without interpreting path text as an authority: the network path host branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28006

Reject malformed redirect authorities without interpreting path text as an authority: path remains case sensitive · case 01

Reject malformed redirect authorities without interpreting path text as an authority: the path remains case sensitive branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28007

Reject malformed redirect authorities without interpreting path text as an authority: path remains case sensitive · case 02

Reject malformed redirect authorities without interpreting path text as an authority: the path remains case sensitive branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28008

Reject malformed redirect authorities without interpreting path text as an authority: path remains case sensitive · case 03

Reject malformed redirect authorities without interpreting path text as an authority: the path remains case sensitive branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28009

Reject malformed redirect authorities without interpreting path text as an authority: path remains case sensitive · case 04

Reject malformed redirect authorities without interpreting path text as an authority: the path remains case sensitive branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28010

Reject malformed redirect authorities without interpreting path text as an authority: path remains case sensitive · case 05

Reject malformed redirect authorities without interpreting path text as an authority: the path remains case sensitive branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28011

Reject malformed redirect authorities without interpreting path text as an authority: empty path request target · case 01

Reject malformed redirect authorities without interpreting path text as an authority: the empty path request target branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28012

Reject malformed redirect authorities without interpreting path text as an authority: empty path request target · case 02

Reject malformed redirect authorities without interpreting path text as an authority: the empty path request target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28013

Reject malformed redirect authorities without interpreting path text as an authority: empty path request target · case 03

Reject malformed redirect authorities without interpreting path text as an authority: the empty path request target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28014

Reject malformed redirect authorities without interpreting path text as an authority: empty path request target · case 04

Reject malformed redirect authorities without interpreting path text as an authority: the empty path request target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28015

Reject malformed redirect authorities without interpreting path text as an authority: empty path request target · case 05

Reject malformed redirect authorities without interpreting path text as an authority: the empty path request target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28016

Validate a redirect port against an explicit bounded port policy: omission default · case 01

Validate a redirect port against an explicit bounded port policy: the omission default branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28017

Validate a redirect port against an explicit bounded port policy: omission default · case 02

Validate a redirect port against an explicit bounded port policy: the omission default branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28018

Validate a redirect port against an explicit bounded port policy: omission default · case 03

Validate a redirect port against an explicit bounded port policy: the omission default branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28019

Validate a redirect port against an explicit bounded port policy: omission default · case 04

Validate a redirect port against an explicit bounded port policy: the omission default branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28020

Validate a redirect port against an explicit bounded port policy: omission default · case 05

Validate a redirect port against an explicit bounded port policy: the omission default branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28021

Validate a redirect port against an explicit bounded port policy: zero port rejection · case 01

Validate a redirect port against an explicit bounded port policy: the zero port rejection branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28022

Validate a redirect port against an explicit bounded port policy: zero port rejection · case 02

Validate a redirect port against an explicit bounded port policy: the zero port rejection branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28023

Validate a redirect port against an explicit bounded port policy: zero port rejection · case 03

Validate a redirect port against an explicit bounded port policy: the zero port rejection branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28024

Validate a redirect port against an explicit bounded port policy: zero port rejection · case 04

Validate a redirect port against an explicit bounded port policy: the zero port rejection branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28025

Validate a redirect port against an explicit bounded port policy: zero port rejection · case 05

Validate a redirect port against an explicit bounded port policy: the zero port rejection branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28026

Validate a redirect port against an explicit bounded port policy: port upper bound · case 01

Validate a redirect port against an explicit bounded port policy: the port upper bound branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28027

Validate a redirect port against an explicit bounded port policy: port upper bound · case 02

Validate a redirect port against an explicit bounded port policy: the port upper bound branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28028

Validate a redirect port against an explicit bounded port policy: port upper bound · case 03

Validate a redirect port against an explicit bounded port policy: the port upper bound branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28029

Validate a redirect port against an explicit bounded port policy: port upper bound · case 04

Validate a redirect port against an explicit bounded port policy: the port upper bound branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28030

Validate a redirect port against an explicit bounded port policy: port upper bound · case 05

Validate a redirect port against an explicit bounded port policy: the port upper bound branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28031

Validate a redirect port against an explicit bounded port policy: negative port rejection · case 01

Validate a redirect port against an explicit bounded port policy: the negative port rejection branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28032

Validate a redirect port against an explicit bounded port policy: negative port rejection · case 02

Validate a redirect port against an explicit bounded port policy: the negative port rejection branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28033

Validate a redirect port against an explicit bounded port policy: negative port rejection · case 03

Validate a redirect port against an explicit bounded port policy: the negative port rejection branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28034

Validate a redirect port against an explicit bounded port policy: negative port rejection · case 04

Validate a redirect port against an explicit bounded port policy: the negative port rejection branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28035

Validate a redirect port against an explicit bounded port policy: negative port rejection · case 05

Validate a redirect port against an explicit bounded port policy: the negative port rejection branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28036

Validate a redirect port against an explicit bounded port policy: explicit port allowlist · case 01

Validate a redirect port against an explicit bounded port policy: the explicit port allowlist branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28037

Validate a redirect port against an explicit bounded port policy: explicit port allowlist · case 02

Validate a redirect port against an explicit bounded port policy: the explicit port allowlist branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28038

Validate a redirect port against an explicit bounded port policy: explicit port allowlist · case 03

Validate a redirect port against an explicit bounded port policy: the explicit port allowlist branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28039

Validate a redirect port against an explicit bounded port policy: explicit port allowlist · case 04

Validate a redirect port against an explicit bounded port policy: the explicit port allowlist branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28040

Validate a redirect port against an explicit bounded port policy: explicit port allowlist · case 05

Validate a redirect port against an explicit bounded port policy: the explicit port allowlist branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28041

Keep encoded path structure distinct from redirect routing structure: encoded slash preservation · case 01

Keep encoded path structure distinct from redirect routing structure: the encoded slash preservation branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28042

Keep encoded path structure distinct from redirect routing structure: encoded slash preservation · case 02

Keep encoded path structure distinct from redirect routing structure: the encoded slash preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28043

Keep encoded path structure distinct from redirect routing structure: encoded slash preservation · case 03

Keep encoded path structure distinct from redirect routing structure: the encoded slash preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28044

Keep encoded path structure distinct from redirect routing structure: encoded slash preservation · case 04

Keep encoded path structure distinct from redirect routing structure: the encoded slash preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28045

Keep encoded path structure distinct from redirect routing structure: encoded slash preservation · case 05

Keep encoded path structure distinct from redirect routing structure: the encoded slash preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28046

Keep encoded path structure distinct from redirect routing structure: query not path · case 01

Keep encoded path structure distinct from redirect routing structure: the query not path branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28047

Keep encoded path structure distinct from redirect routing structure: query not path · case 02

Keep encoded path structure distinct from redirect routing structure: the query not path branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28048

Keep encoded path structure distinct from redirect routing structure: query not path · case 03

Keep encoded path structure distinct from redirect routing structure: the query not path branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28049

Keep encoded path structure distinct from redirect routing structure: query not path · case 04

Keep encoded path structure distinct from redirect routing structure: the query not path branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28050

Keep encoded path structure distinct from redirect routing structure: query not path · case 05

Keep encoded path structure distinct from redirect routing structure: the query not path branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28051

Keep encoded path structure distinct from redirect routing structure: literal plus preservation · case 01

Keep encoded path structure distinct from redirect routing structure: the literal plus preservation branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28052

Keep encoded path structure distinct from redirect routing structure: literal plus preservation · case 02

Keep encoded path structure distinct from redirect routing structure: the literal plus preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28053

Keep encoded path structure distinct from redirect routing structure: literal plus preservation · case 03

Keep encoded path structure distinct from redirect routing structure: the literal plus preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28054

Keep encoded path structure distinct from redirect routing structure: literal plus preservation · case 04

Keep encoded path structure distinct from redirect routing structure: the literal plus preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28055

Keep encoded path structure distinct from redirect routing structure: literal plus preservation · case 05

Keep encoded path structure distinct from redirect routing structure: the literal plus preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28056

Keep encoded path structure distinct from redirect routing structure: one percent decode · case 01

Keep encoded path structure distinct from redirect routing structure: the one percent decode branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28057

Keep encoded path structure distinct from redirect routing structure: one percent decode · case 02

Keep encoded path structure distinct from redirect routing structure: the one percent decode branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28058

Keep encoded path structure distinct from redirect routing structure: one percent decode · case 03

Keep encoded path structure distinct from redirect routing structure: the one percent decode branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28059

Keep encoded path structure distinct from redirect routing structure: one percent decode · case 04

Keep encoded path structure distinct from redirect routing structure: the one percent decode branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28060

Keep encoded path structure distinct from redirect routing structure: one percent decode · case 05

Keep encoded path structure distinct from redirect routing structure: the one percent decode branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28061

Keep encoded path structure distinct from redirect routing structure: dot segment recognition · case 01

Keep encoded path structure distinct from redirect routing structure: the dot segment recognition branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28062

Keep encoded path structure distinct from redirect routing structure: dot segment recognition · case 02

Keep encoded path structure distinct from redirect routing structure: the dot segment recognition branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28063

Keep encoded path structure distinct from redirect routing structure: dot segment recognition · case 03

Keep encoded path structure distinct from redirect routing structure: the dot segment recognition branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28064

Keep encoded path structure distinct from redirect routing structure: dot segment recognition · case 04

Keep encoded path structure distinct from redirect routing structure: the dot segment recognition branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28065

Keep encoded path structure distinct from redirect routing structure: dot segment recognition · case 05

Keep encoded path structure distinct from redirect routing structure: the dot segment recognition branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28066

Preserve query-field structure while preparing a redirect target: duplicate key preservation · case 01

Preserve query-field structure while preparing a redirect target: the duplicate key preservation branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28067

Preserve query-field structure while preparing a redirect target: duplicate key preservation · case 02

Preserve query-field structure while preparing a redirect target: the duplicate key preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28068

Preserve query-field structure while preparing a redirect target: duplicate key preservation · case 03

Preserve query-field structure while preparing a redirect target: the duplicate key preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28069

Preserve query-field structure while preparing a redirect target: duplicate key preservation · case 04

Preserve query-field structure while preparing a redirect target: the duplicate key preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28070

Preserve query-field structure while preparing a redirect target: duplicate key preservation · case 05

Preserve query-field structure while preparing a redirect target: the duplicate key preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28071

Preserve query-field structure while preparing a redirect target: bare vs empty value · case 01

Preserve query-field structure while preparing a redirect target: the bare vs empty value branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28072

Preserve query-field structure while preparing a redirect target: bare vs empty value · case 02

Preserve query-field structure while preparing a redirect target: the bare vs empty value branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28073

Preserve query-field structure while preparing a redirect target: bare vs empty value · case 03

Preserve query-field structure while preparing a redirect target: the bare vs empty value branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28074

Preserve query-field structure while preparing a redirect target: bare vs empty value · case 04

Preserve query-field structure while preparing a redirect target: the bare vs empty value branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28075

Preserve query-field structure while preparing a redirect target: bare vs empty value · case 05

Preserve query-field structure while preparing a redirect target: the bare vs empty value branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28076

Preserve query-field structure while preparing a redirect target: first equals boundary · case 01

Preserve query-field structure while preparing a redirect target: the first equals boundary branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28077

Preserve query-field structure while preparing a redirect target: first equals boundary · case 02

Preserve query-field structure while preparing a redirect target: the first equals boundary branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28078

Preserve query-field structure while preparing a redirect target: first equals boundary · case 03

Preserve query-field structure while preparing a redirect target: the first equals boundary branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28079

Preserve query-field structure while preparing a redirect target: first equals boundary · case 04

Preserve query-field structure while preparing a redirect target: the first equals boundary branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28080

Preserve query-field structure while preparing a redirect target: first equals boundary · case 05

Preserve query-field structure while preparing a redirect target: the first equals boundary branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28081

Preserve query-field structure while preparing a redirect target: semicolon is data · case 01

Preserve query-field structure while preparing a redirect target: the semicolon is data branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28082

Preserve query-field structure while preparing a redirect target: semicolon is data · case 02

Preserve query-field structure while preparing a redirect target: the semicolon is data branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28083

Preserve query-field structure while preparing a redirect target: semicolon is data · case 03

Preserve query-field structure while preparing a redirect target: the semicolon is data branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28084

Preserve query-field structure while preparing a redirect target: semicolon is data · case 04

Preserve query-field structure while preparing a redirect target: the semicolon is data branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28085

Preserve query-field structure while preparing a redirect target: semicolon is data · case 05

Preserve query-field structure while preparing a redirect target: the semicolon is data branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28086

Preserve query-field structure while preparing a redirect target: encoded delimiter preservation · case 01

Preserve query-field structure while preparing a redirect target: the encoded delimiter preservation branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28087

Preserve query-field structure while preparing a redirect target: encoded delimiter preservation · case 02

Preserve query-field structure while preparing a redirect target: the encoded delimiter preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28088

Preserve query-field structure while preparing a redirect target: encoded delimiter preservation · case 03

Preserve query-field structure while preparing a redirect target: the encoded delimiter preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28089

Preserve query-field structure while preparing a redirect target: encoded delimiter preservation · case 04

Preserve query-field structure while preparing a redirect target: the encoded delimiter preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28090

Preserve query-field structure while preparing a redirect target: encoded delimiter preservation · case 05

Preserve query-field structure while preparing a redirect target: the encoded delimiter preservation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28091

Commit redirect history only after target admission: pending entry commit · case 01

Commit redirect history only after target admission: the pending entry commit branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28092

Commit redirect history only after target admission: pending entry commit · case 02

Commit redirect history only after target admission: the pending entry commit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28093

Commit redirect history only after target admission: pending entry commit · case 03

Commit redirect history only after target admission: the pending entry commit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28094

Commit redirect history only after target admission: pending entry commit · case 04

Commit redirect history only after target admission: the pending entry commit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28095

Commit redirect history only after target admission: pending entry commit · case 05

Commit redirect history only after target admission: the pending entry commit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28096

Commit redirect history only after target admission: chronological order · case 01

Commit redirect history only after target admission: the chronological order branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-28097

Commit redirect history only after target admission: chronological order · case 02

Commit redirect history only after target admission: the chronological order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28098

Commit redirect history only after target admission: chronological order · case 03

Commit redirect history only after target admission: the chronological order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28099

Commit redirect history only after target admission: chronological order · case 04

Commit redirect history only after target admission: the chronological order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-28100

Commit redirect history only after target admission: chronological order · case 05

Commit redirect history only after target admission: the chronological order branch emits an incorrect decision.

HTTP redirects◈ Members↗

INSPECTABLE BY DESIGN

Every result has a runnable source.

Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.

Read the methodology ↗