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-29001

Invalidate redirect mappings by source and affected target with partition isolation: incoming target removal · case 01

Invalidate redirect mappings by source and affected target with partition isolation: the incoming target removal branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29002

Invalidate redirect mappings by source and affected target with partition isolation: incoming target removal · case 02

Invalidate redirect mappings by source and affected target with partition isolation: the incoming target removal branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29003

Invalidate redirect mappings by source and affected target with partition isolation: incoming target removal · case 03

Invalidate redirect mappings by source and affected target with partition isolation: the incoming target removal branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29004

Invalidate redirect mappings by source and affected target with partition isolation: incoming target removal · case 04

Invalidate redirect mappings by source and affected target with partition isolation: the incoming target removal branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29005

Invalidate redirect mappings by source and affected target with partition isolation: incoming target removal · case 05

Invalidate redirect mappings by source and affected target with partition isolation: the incoming target removal branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29006

Invalidate redirect mappings by source and affected target with partition isolation: permanence filter · case 01

Invalidate redirect mappings by source and affected target with partition isolation: the permanence filter branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29007

Invalidate redirect mappings by source and affected target with partition isolation: permanence filter · case 02

Invalidate redirect mappings by source and affected target with partition isolation: the permanence filter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29008

Invalidate redirect mappings by source and affected target with partition isolation: permanence filter · case 03

Invalidate redirect mappings by source and affected target with partition isolation: the permanence filter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29009

Invalidate redirect mappings by source and affected target with partition isolation: permanence filter · case 04

Invalidate redirect mappings by source and affected target with partition isolation: the permanence filter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29010

Invalidate redirect mappings by source and affected target with partition isolation: permanence filter · case 05

Invalidate redirect mappings by source and affected target with partition isolation: the permanence filter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29011

Invalidate redirect mappings by source and affected target with partition isolation: affected source report · case 01

Invalidate redirect mappings by source and affected target with partition isolation: the affected source report branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29012

Invalidate redirect mappings by source and affected target with partition isolation: affected source report · case 02

Invalidate redirect mappings by source and affected target with partition isolation: the affected source report branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29013

Invalidate redirect mappings by source and affected target with partition isolation: affected source report · case 03

Invalidate redirect mappings by source and affected target with partition isolation: the affected source report branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29014

Invalidate redirect mappings by source and affected target with partition isolation: affected source report · case 04

Invalidate redirect mappings by source and affected target with partition isolation: the affected source report branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29015

Invalidate redirect mappings by source and affected target with partition isolation: affected source report · case 05

Invalidate redirect mappings by source and affected target with partition isolation: the affected source report branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29016

Invalidate redirect mappings by source and affected target with partition isolation: removed entry count · case 01

Invalidate redirect mappings by source and affected target with partition isolation: the removed entry count branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29017

Invalidate redirect mappings by source and affected target with partition isolation: removed entry count · case 02

Invalidate redirect mappings by source and affected target with partition isolation: the removed entry count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29018

Invalidate redirect mappings by source and affected target with partition isolation: removed entry count · case 03

Invalidate redirect mappings by source and affected target with partition isolation: the removed entry count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29019

Invalidate redirect mappings by source and affected target with partition isolation: removed entry count · case 04

Invalidate redirect mappings by source and affected target with partition isolation: the removed entry count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29020

Invalidate redirect mappings by source and affected target with partition isolation: removed entry count · case 05

Invalidate redirect mappings by source and affected target with partition isolation: the removed entry count branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29021

Invalidate redirect mappings by source and affected target with partition isolation: partition exactness · case 01

Invalidate redirect mappings by source and affected target with partition isolation: the partition exactness branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29022

Invalidate redirect mappings by source and affected target with partition isolation: partition exactness · case 02

Invalidate redirect mappings by source and affected target with partition isolation: the partition exactness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29023

Invalidate redirect mappings by source and affected target with partition isolation: partition exactness · case 03

Invalidate redirect mappings by source and affected target with partition isolation: the partition exactness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29024

Invalidate redirect mappings by source and affected target with partition isolation: partition exactness · case 04

Invalidate redirect mappings by source and affected target with partition isolation: the partition exactness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29025

Invalidate redirect mappings by source and affected target with partition isolation: partition exactness · case 05

Invalidate redirect mappings by source and affected target with partition isolation: the partition exactness branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29026

Invalidate redirect mappings by source and affected target with partition isolation: empty invalidation no hit · case 01

Invalidate redirect mappings by source and affected target with partition isolation: the empty invalidation no hit branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29027

Invalidate redirect mappings by source and affected target with partition isolation: empty invalidation no hit · case 02

Invalidate redirect mappings by source and affected target with partition isolation: the empty invalidation no hit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29028

Invalidate redirect mappings by source and affected target with partition isolation: empty invalidation no hit · case 03

Invalidate redirect mappings by source and affected target with partition isolation: the empty invalidation no hit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29029

Invalidate redirect mappings by source and affected target with partition isolation: empty invalidation no hit · case 04

Invalidate redirect mappings by source and affected target with partition isolation: the empty invalidation no hit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29030

Invalidate redirect mappings by source and affected target with partition isolation: empty invalidation no hit · case 05

Invalidate redirect mappings by source and affected target with partition isolation: the empty invalidation no hit branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29031

Invalidate redirect mappings by source and affected target with partition isolation: source target direction · case 01

Invalidate redirect mappings by source and affected target with partition isolation: the source target direction branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29032

Invalidate redirect mappings by source and affected target with partition isolation: source target direction · case 02

Invalidate redirect mappings by source and affected target with partition isolation: the source target direction branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29033

Invalidate redirect mappings by source and affected target with partition isolation: source target direction · case 03

Invalidate redirect mappings by source and affected target with partition isolation: the source target direction branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29034

Invalidate redirect mappings by source and affected target with partition isolation: source target direction · case 04

Invalidate redirect mappings by source and affected target with partition isolation: the source target direction branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29035

Invalidate redirect mappings by source and affected target with partition isolation: source target direction · case 05

Invalidate redirect mappings by source and affected target with partition isolation: the source target direction branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29036

Invalidate redirect mappings by source and affected target with partition isolation: survivor order · case 01

Invalidate redirect mappings by source and affected target with partition isolation: the survivor order branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29037

Invalidate redirect mappings by source and affected target with partition isolation: survivor order · case 02

Invalidate redirect mappings by source and affected target with partition isolation: the survivor order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29038

Invalidate redirect mappings by source and affected target with partition isolation: survivor order · case 03

Invalidate redirect mappings by source and affected target with partition isolation: the survivor order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29039

Invalidate redirect mappings by source and affected target with partition isolation: survivor order · case 04

Invalidate redirect mappings by source and affected target with partition isolation: the survivor order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29040

Invalidate redirect mappings by source and affected target with partition isolation: survivor order · case 05

Invalidate redirect mappings by source and affected target with partition isolation: the survivor order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29041

Build public redirect origins from explicitly trusted proxy metadata: trust gates forwarded host · case 01

Build public redirect origins from explicitly trusted proxy metadata: the trust gates forwarded host branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29042

Build public redirect origins from explicitly trusted proxy metadata: trust gates forwarded host · case 02

Build public redirect origins from explicitly trusted proxy metadata: the trust gates forwarded host branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29043

Build public redirect origins from explicitly trusted proxy metadata: trust gates forwarded host · case 03

Build public redirect origins from explicitly trusted proxy metadata: the trust gates forwarded host branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29044

Build public redirect origins from explicitly trusted proxy metadata: trust gates forwarded host · case 04

Build public redirect origins from explicitly trusted proxy metadata: the trust gates forwarded host branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29045

Build public redirect origins from explicitly trusted proxy metadata: trust gates forwarded host · case 05

Build public redirect origins from explicitly trusted proxy metadata: the trust gates forwarded host branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29046

Build public redirect origins from explicitly trusted proxy metadata: trusted proto fallback · case 01

Build public redirect origins from explicitly trusted proxy metadata: the trusted proto fallback branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29047

Build public redirect origins from explicitly trusted proxy metadata: trusted proto fallback · case 02

Build public redirect origins from explicitly trusted proxy metadata: the trusted proto fallback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29048

Build public redirect origins from explicitly trusted proxy metadata: trusted proto fallback · case 03

Build public redirect origins from explicitly trusted proxy metadata: the trusted proto fallback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29049

Build public redirect origins from explicitly trusted proxy metadata: trusted proto fallback · case 04

Build public redirect origins from explicitly trusted proxy metadata: the trusted proto fallback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29050

Build public redirect origins from explicitly trusted proxy metadata: trusted proto fallback · case 05

Build public redirect origins from explicitly trusted proxy metadata: the trusted proto fallback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29051

Build public redirect origins from explicitly trusted proxy metadata: proxy chain order · case 01

Build public redirect origins from explicitly trusted proxy metadata: the proxy chain order branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29052

Build public redirect origins from explicitly trusted proxy metadata: proxy chain order · case 02

Build public redirect origins from explicitly trusted proxy metadata: the proxy chain order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29053

Build public redirect origins from explicitly trusted proxy metadata: proxy chain order · case 03

Build public redirect origins from explicitly trusted proxy metadata: the proxy chain order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29054

Build public redirect origins from explicitly trusted proxy metadata: proxy chain order · case 04

Build public redirect origins from explicitly trusted proxy metadata: the proxy chain order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29055

Build public redirect origins from explicitly trusted proxy metadata: proxy chain order · case 05

Build public redirect origins from explicitly trusted proxy metadata: the proxy chain order branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29056

Build public redirect origins from explicitly trusted proxy metadata: empty forwarded value fallback · case 01

Build public redirect origins from explicitly trusted proxy metadata: the empty forwarded value fallback branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29057

Build public redirect origins from explicitly trusted proxy metadata: empty forwarded value fallback · case 02

Build public redirect origins from explicitly trusted proxy metadata: the empty forwarded value fallback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29058

Build public redirect origins from explicitly trusted proxy metadata: empty forwarded value fallback · case 03

Build public redirect origins from explicitly trusted proxy metadata: the empty forwarded value fallback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29059

Build public redirect origins from explicitly trusted proxy metadata: empty forwarded value fallback · case 04

Build public redirect origins from explicitly trusted proxy metadata: the empty forwarded value fallback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29060

Build public redirect origins from explicitly trusted proxy metadata: empty forwarded value fallback · case 05

Build public redirect origins from explicitly trusted proxy metadata: the empty forwarded value fallback branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29061

Build public redirect origins from explicitly trusted proxy metadata: prefix not authority · case 01

Build public redirect origins from explicitly trusted proxy metadata: the prefix not authority branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29062

Build public redirect origins from explicitly trusted proxy metadata: prefix not authority · case 02

Build public redirect origins from explicitly trusted proxy metadata: the prefix not authority branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29063

Build public redirect origins from explicitly trusted proxy metadata: prefix not authority · case 03

Build public redirect origins from explicitly trusted proxy metadata: the prefix not authority branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29064

Build public redirect origins from explicitly trusted proxy metadata: prefix not authority · case 04

Build public redirect origins from explicitly trusted proxy metadata: the prefix not authority branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29065

Build public redirect origins from explicitly trusted proxy metadata: prefix not authority · case 05

Build public redirect origins from explicitly trusted proxy metadata: the prefix not authority branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29066

Build public redirect origins from explicitly trusted proxy metadata: ignore untrusted prefix · case 01

Build public redirect origins from explicitly trusted proxy metadata: the ignore untrusted prefix branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29067

Build public redirect origins from explicitly trusted proxy metadata: ignore untrusted prefix · case 02

Build public redirect origins from explicitly trusted proxy metadata: the ignore untrusted prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29068

Build public redirect origins from explicitly trusted proxy metadata: ignore untrusted prefix · case 03

Build public redirect origins from explicitly trusted proxy metadata: the ignore untrusted prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29069

Build public redirect origins from explicitly trusted proxy metadata: ignore untrusted prefix · case 04

Build public redirect origins from explicitly trusted proxy metadata: the ignore untrusted prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29070

Build public redirect origins from explicitly trusted proxy metadata: ignore untrusted prefix · case 05

Build public redirect origins from explicitly trusted proxy metadata: the ignore untrusted prefix branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29071

Build public redirect origins from explicitly trusted proxy metadata: direct authority port preserved · case 01

Build public redirect origins from explicitly trusted proxy metadata: the direct authority port preserved branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29072

Build public redirect origins from explicitly trusted proxy metadata: direct authority port preserved · case 02

Build public redirect origins from explicitly trusted proxy metadata: the direct authority port preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29073

Build public redirect origins from explicitly trusted proxy metadata: direct authority port preserved · case 03

Build public redirect origins from explicitly trusted proxy metadata: the direct authority port preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29074

Build public redirect origins from explicitly trusted proxy metadata: direct authority port preserved · case 04

Build public redirect origins from explicitly trusted proxy metadata: the direct authority port preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29075

Build public redirect origins from explicitly trusted proxy metadata: direct authority port preserved · case 05

Build public redirect origins from explicitly trusted proxy metadata: the direct authority port preserved branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29076

Build public redirect origins from explicitly trusted proxy metadata: prefix single terminal delimiter · case 01

Build public redirect origins from explicitly trusted proxy metadata: the prefix single terminal delimiter branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29077

Build public redirect origins from explicitly trusted proxy metadata: prefix single terminal delimiter · case 02

Build public redirect origins from explicitly trusted proxy metadata: the prefix single terminal delimiter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29078

Build public redirect origins from explicitly trusted proxy metadata: prefix single terminal delimiter · case 03

Build public redirect origins from explicitly trusted proxy metadata: the prefix single terminal delimiter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29079

Build public redirect origins from explicitly trusted proxy metadata: prefix single terminal delimiter · case 04

Build public redirect origins from explicitly trusted proxy metadata: the prefix single terminal delimiter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29080

Build public redirect origins from explicitly trusted proxy metadata: prefix single terminal delimiter · case 05

Build public redirect origins from explicitly trusted proxy metadata: the prefix single terminal delimiter branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29081

Build public redirect origins from explicitly trusted proxy metadata: scheme syntax validation · case 01

Build public redirect origins from explicitly trusted proxy metadata: the scheme syntax validation branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29082

Build public redirect origins from explicitly trusted proxy metadata: scheme syntax validation · case 02

Build public redirect origins from explicitly trusted proxy metadata: the scheme syntax validation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29083

Build public redirect origins from explicitly trusted proxy metadata: scheme syntax validation · case 03

Build public redirect origins from explicitly trusted proxy metadata: the scheme syntax validation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29084

Build public redirect origins from explicitly trusted proxy metadata: scheme syntax validation · case 04

Build public redirect origins from explicitly trusted proxy metadata: the scheme syntax validation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29085

Build public redirect origins from explicitly trusted proxy metadata: scheme syntax validation · case 05

Build public redirect origins from explicitly trusted proxy metadata: the scheme syntax validation branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29086

Build public redirect origins from explicitly trusted proxy metadata: proxy metadata provenance · case 01

Build public redirect origins from explicitly trusted proxy metadata: the proxy metadata provenance branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29087

Build public redirect origins from explicitly trusted proxy metadata: proxy metadata provenance · case 02

Build public redirect origins from explicitly trusted proxy metadata: the proxy metadata provenance branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29088

Build public redirect origins from explicitly trusted proxy metadata: proxy metadata provenance · case 03

Build public redirect origins from explicitly trusted proxy metadata: the proxy metadata provenance branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29089

Build public redirect origins from explicitly trusted proxy metadata: proxy metadata provenance · case 04

Build public redirect origins from explicitly trusted proxy metadata: the proxy metadata provenance branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29090

Build public redirect origins from explicitly trusted proxy metadata: proxy metadata provenance · case 05

Build public redirect origins from explicitly trusted proxy metadata: the proxy metadata provenance branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29091

Canonicalize a directory URL after resource lookup without redirecting regular files: directory only slash · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the directory only slash branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29092

Canonicalize a directory URL after resource lookup without redirecting regular files: directory only slash · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the directory only slash branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29093

Canonicalize a directory URL after resource lookup without redirecting regular files: directory only slash · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the directory only slash branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29094

Canonicalize a directory URL after resource lookup without redirecting regular files: directory only slash · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the directory only slash branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29095

Canonicalize a directory URL after resource lookup without redirecting regular files: directory only slash · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the directory only slash branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29096

Canonicalize a directory URL after resource lookup without redirecting regular files: single slash target · case 01

Canonicalize a directory URL after resource lookup without redirecting regular files: the single slash target branch emits an incorrect decision.

HTTP redirects● Open access↗
FA-29097

Canonicalize a directory URL after resource lookup without redirecting regular files: single slash target · case 02

Canonicalize a directory URL after resource lookup without redirecting regular files: the single slash target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29098

Canonicalize a directory URL after resource lookup without redirecting regular files: single slash target · case 03

Canonicalize a directory URL after resource lookup without redirecting regular files: the single slash target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29099

Canonicalize a directory URL after resource lookup without redirecting regular files: single slash target · case 04

Canonicalize a directory URL after resource lookup without redirecting regular files: the single slash target branch emits an incorrect decision.

HTTP redirects◈ Members↗
FA-29100

Canonicalize a directory URL after resource lookup without redirecting regular files: single slash target · case 05

Canonicalize a directory URL after resource lookup without redirecting regular files: the single slash target 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 ↗