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 ↗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
Validate raw target text before any URL normalization: nul detection · case 01
An interior NUL evades validation.
Validate raw target text before any URL normalization: nul detection · case 02
An interior NUL evades validation.
Validate raw target text before any URL normalization: nul detection · case 03
An interior NUL evades validation.
Validate raw target text before any URL normalization: nul detection · case 04
An interior NUL evades validation.
Validate raw target text before any URL normalization: nul detection · case 05
An interior NUL evades validation.
Validate raw target text before any URL normalization: percent triplet · case 01
A malformed escape is accepted or every encoded character is rejected.
Validate raw target text before any URL normalization: percent triplet · case 02
A malformed escape is accepted or every encoded character is rejected.
Validate raw target text before any URL normalization: percent triplet · case 03
A malformed escape is accepted or every encoded character is rejected.
Validate raw target text before any URL normalization: percent triplet · case 04
A malformed escape is accepted or every encoded character is rejected.
Validate raw target text before any URL normalization: percent triplet · case 05
A malformed escape is accepted or every encoded character is rejected.
Validate raw target text before any URL normalization: backslash rejection · case 01
A backslash inside a redirect target reaches a different downstream parser.
Validate raw target text before any URL normalization: backslash rejection · case 02
A backslash inside a redirect target reaches a different downstream parser.
Validate raw target text before any URL normalization: backslash rejection · case 03
A backslash inside a redirect target reaches a different downstream parser.
Validate raw target text before any URL normalization: backslash rejection · case 04
A backslash inside a redirect target reaches a different downstream parser.
Validate raw target text before any URL normalization: backslash rejection · case 05
A backslash inside a redirect target reaches a different downstream parser.
Apply a configured HTTP redirect scheme policy: scheme case fold · case 01
Mixed-case schemes do not compare against policy names.
Apply a configured HTTP redirect scheme policy: scheme case fold · case 02
Mixed-case schemes do not compare against policy names.
Apply a configured HTTP redirect scheme policy: scheme case fold · case 03
Mixed-case schemes do not compare against policy names.
Apply a configured HTTP redirect scheme policy: scheme case fold · case 04
Mixed-case schemes do not compare against policy names.
Apply a configured HTTP redirect scheme policy: scheme case fold · case 05
Mixed-case schemes do not compare against policy names.
Apply a configured HTTP redirect scheme policy: relative target admission · case 01
Relative references disregard the caller policy.
Apply a configured HTTP redirect scheme policy: relative target admission · case 02
Relative references disregard the caller policy.
Apply a configured HTTP redirect scheme policy: relative target admission · case 03
Relative references disregard the caller policy.
Apply a configured HTTP redirect scheme policy: relative target admission · case 04
Relative references disregard the caller policy.
Apply a configured HTTP redirect scheme policy: relative target admission · case 05
Relative references disregard the caller policy.
Apply a configured HTTP redirect scheme policy: non network rejection · case 01
Non-network targets are not consistently rejected.
Apply a configured HTTP redirect scheme policy: non network rejection · case 02
Non-network targets are not consistently rejected.
Apply a configured HTTP redirect scheme policy: non network rejection · case 03
Non-network targets are not consistently rejected.
Apply a configured HTTP redirect scheme policy: non network rejection · case 04
Non-network targets are not consistently rejected.
Apply a configured HTTP redirect scheme policy: non network rejection · case 05
Non-network targets are not consistently rejected.
Apply a configured HTTP redirect scheme policy: upgrade classification · case 01
Same-scheme and downgrade transitions are labeled upgrades.
Apply a configured HTTP redirect scheme policy: upgrade classification · case 02
Same-scheme and downgrade transitions are labeled upgrades.
Apply a configured HTTP redirect scheme policy: upgrade classification · case 03
Same-scheme and downgrade transitions are labeled upgrades.
Apply a configured HTTP redirect scheme policy: upgrade classification · case 04
Same-scheme and downgrade transitions are labeled upgrades.
Apply a configured HTTP redirect scheme policy: upgrade classification · case 05
Same-scheme and downgrade transitions are labeled upgrades.
Apply a configured HTTP redirect scheme policy: implicit scheme upgrade · case 01
An explicit scheme is overwritten by automatic upgrade policy.
Apply a configured HTTP redirect scheme policy: implicit scheme upgrade · case 02
An explicit scheme is overwritten by automatic upgrade policy.
Apply a configured HTTP redirect scheme policy: implicit scheme upgrade · case 03
An explicit scheme is overwritten by automatic upgrade policy.
Apply a configured HTTP redirect scheme policy: implicit scheme upgrade · case 04
An explicit scheme is overwritten by automatic upgrade policy.
Apply a configured HTTP redirect scheme policy: implicit scheme upgrade · case 05
An explicit scheme is overwritten by automatic upgrade policy.
Prepare a redirect replay from a bounded upload cursor: rewind origin · case 01
Replay rewinds to the stream origin instead of the request segment origin.
Prepare a redirect replay from a bounded upload cursor: rewind origin · case 02
Replay rewinds to the stream origin instead of the request segment origin.
Prepare a redirect replay from a bounded upload cursor: rewind origin · case 03
Replay rewinds to the stream origin instead of the request segment origin.
Prepare a redirect replay from a bounded upload cursor: rewind origin · case 04
Replay rewinds to the stream origin instead of the request segment origin.
Prepare a redirect replay from a bounded upload cursor: rewind origin · case 05
Replay rewinds to the stream origin instead of the request segment origin.
Prepare a redirect replay from a bounded upload cursor: remaining segment · case 01
A segment-relative cursor is treated as an absolute count.
Prepare a redirect replay from a bounded upload cursor: remaining segment · case 02
A segment-relative cursor is treated as an absolute count.
Prepare a redirect replay from a bounded upload cursor: remaining segment · case 03
A segment-relative cursor is treated as an absolute count.
Prepare a redirect replay from a bounded upload cursor: remaining segment · case 04
A segment-relative cursor is treated as an absolute count.
Prepare a redirect replay from a bounded upload cursor: remaining segment · case 05
A segment-relative cursor is treated as an absolute count.
Prepare a redirect replay from a bounded upload cursor: nonseekable consumption · case 01
An untouched one-shot body or a discarded body is rejected.
Prepare a redirect replay from a bounded upload cursor: nonseekable consumption · case 02
An untouched one-shot body or a discarded body is rejected.
Prepare a redirect replay from a bounded upload cursor: nonseekable consumption · case 03
An untouched one-shot body or a discarded body is rejected.
Prepare a redirect replay from a bounded upload cursor: nonseekable consumption · case 04
An untouched one-shot body or a discarded body is rejected.
Prepare a redirect replay from a bounded upload cursor: nonseekable consumption · case 05
An untouched one-shot body or a discarded body is rejected.
Prepare a redirect replay from a bounded upload cursor: discarded body length · case 01
A body-dropping redirect advertises the old payload length.
Prepare a redirect replay from a bounded upload cursor: discarded body length · case 02
A body-dropping redirect advertises the old payload length.
Prepare a redirect replay from a bounded upload cursor: discarded body length · case 03
A body-dropping redirect advertises the old payload length.
Prepare a redirect replay from a bounded upload cursor: discarded body length · case 04
A body-dropping redirect advertises the old payload length.
Prepare a redirect replay from a bounded upload cursor: discarded body length · case 05
A body-dropping redirect advertises the old payload length.
Prepare a redirect replay from a bounded upload cursor: seek required · case 01
A seek is issued when replay does not require it.
Prepare a redirect replay from a bounded upload cursor: seek required · case 02
A seek is issued when replay does not require it.
Prepare a redirect replay from a bounded upload cursor: seek required · case 03
A seek is issued when replay does not require it.
Prepare a redirect replay from a bounded upload cursor: seek required · case 04
A seek is issued when replay does not require it.
Prepare a redirect replay from a bounded upload cursor: seek required · case 05
A seek is issued when replay does not require it.
Prepare upload metadata and handoff sequencing after a redirect decision: entity metadata clearing · case 01
Removing only Content-Length leaves stale entity metadata attached to a rewritten request.
Prepare upload metadata and handoff sequencing after a redirect decision: entity metadata clearing · case 02
Removing only Content-Length leaves stale entity metadata attached to a rewritten request.
Prepare upload metadata and handoff sequencing after a redirect decision: entity metadata clearing · case 03
Removing only Content-Length leaves stale entity metadata attached to a rewritten request.
Prepare upload metadata and handoff sequencing after a redirect decision: entity metadata clearing · case 04
Removing only Content-Length leaves stale entity metadata attached to a rewritten request.
Prepare upload metadata and handoff sequencing after a redirect decision: entity metadata clearing · case 05
Removing only Content-Length leaves stale entity metadata attached to a rewritten request.
Prepare upload metadata and handoff sequencing after a redirect decision: multipart wire boundary · case 01
Reconstructing multipart headers chooses a new boundary although the replayed wire bytes still contain the old boundary.
Prepare upload metadata and handoff sequencing after a redirect decision: multipart wire boundary · case 02
Reconstructing multipart headers chooses a new boundary although the replayed wire bytes still contain the old boundary.
Prepare upload metadata and handoff sequencing after a redirect decision: multipart wire boundary · case 03
Reconstructing multipart headers chooses a new boundary although the replayed wire bytes still contain the old boundary.
Prepare upload metadata and handoff sequencing after a redirect decision: multipart wire boundary · case 04
Reconstructing multipart headers chooses a new boundary although the replayed wire bytes still contain the old boundary.
Prepare upload metadata and handoff sequencing after a redirect decision: multipart wire boundary · case 05
Reconstructing multipart headers chooses a new boundary although the replayed wire bytes still contain the old boundary.
Prepare upload metadata and handoff sequencing after a redirect decision: new request expect handshake · case 01
The new request starts an upload handshake after its method or body emptiness makes that handshake inapplicable.
Prepare upload metadata and handoff sequencing after a redirect decision: new request expect handshake · case 02
The new request starts an upload handshake after its method or body emptiness makes that handshake inapplicable.
Prepare upload metadata and handoff sequencing after a redirect decision: new request expect handshake · case 03
The new request starts an upload handshake after its method or body emptiness makes that handshake inapplicable.
Prepare upload metadata and handoff sequencing after a redirect decision: new request expect handshake · case 04
The new request starts an upload handshake after its method or body emptiness makes that handshake inapplicable.
Prepare upload metadata and handoff sequencing after a redirect decision: new request expect handshake · case 05
The new request starts an upload handshake after its method or body emptiness makes that handshake inapplicable.
Prepare upload metadata and handoff sequencing after a redirect decision: abort before dispatch · case 01
Dispatch races the cancellation of the obsolete upload source.
Prepare upload metadata and handoff sequencing after a redirect decision: abort before dispatch · case 02
Dispatch races the cancellation of the obsolete upload source.
Prepare upload metadata and handoff sequencing after a redirect decision: abort before dispatch · case 03
Dispatch races the cancellation of the obsolete upload source.
Prepare upload metadata and handoff sequencing after a redirect decision: abort before dispatch · case 04
Dispatch races the cancellation of the obsolete upload source.
Prepare upload metadata and handoff sequencing after a redirect decision: abort before dispatch · case 05
Dispatch races the cancellation of the obsolete upload source.
Prepare upload metadata and handoff sequencing after a redirect decision: unknown length framing · case 01
An unknown replay length and a known zero-byte body are assigned the same framing.
Prepare upload metadata and handoff sequencing after a redirect decision: unknown length framing · case 02
An unknown replay length and a known zero-byte body are assigned the same framing.
Prepare upload metadata and handoff sequencing after a redirect decision: unknown length framing · case 03
An unknown replay length and a known zero-byte body are assigned the same framing.
Prepare upload metadata and handoff sequencing after a redirect decision: unknown length framing · case 04
An unknown replay length and a known zero-byte body are assigned the same framing.
Prepare upload metadata and handoff sequencing after a redirect decision: unknown length framing · case 05
An unknown replay length and a known zero-byte body are assigned the same framing.
Reject malformed redirect authorities without interpreting path text as an authority: authority presence · case 01
Reject malformed redirect authorities without interpreting path text as an authority: the authority presence branch emits an incorrect decision.
Reject malformed redirect authorities without interpreting path text as an authority: authority presence · case 02
Reject malformed redirect authorities without interpreting path text as an authority: the authority presence branch emits an incorrect decision.
Reject malformed redirect authorities without interpreting path text as an authority: authority presence · case 03
Reject malformed redirect authorities without interpreting path text as an authority: the authority presence branch emits an incorrect decision.
Reject malformed redirect authorities without interpreting path text as an authority: authority presence · case 04
Reject malformed redirect authorities without interpreting path text as an authority: the authority presence branch emits an incorrect decision.
Reject malformed redirect authorities without interpreting path text as an authority: authority presence · case 05
Reject malformed redirect authorities without interpreting path text as an authority: the authority presence branch emits an incorrect decision.
Reject malformed redirect authorities without interpreting path text as an authority: host lowercase · case 01
Reject malformed redirect authorities without interpreting path text as an authority: the host lowercase branch emits an incorrect decision.
Reject malformed redirect authorities without interpreting path text as an authority: host lowercase · case 02
Reject malformed redirect authorities without interpreting path text as an authority: the host lowercase branch emits an incorrect decision.
Reject malformed redirect authorities without interpreting path text as an authority: host lowercase · case 03
Reject malformed redirect authorities without interpreting path text as an authority: the host lowercase branch emits an incorrect decision.
Reject malformed redirect authorities without interpreting path text as an authority: host lowercase · case 04
Reject malformed redirect authorities without interpreting path text as an authority: the host lowercase branch emits an incorrect decision.
Reject malformed redirect authorities without interpreting path text as an authority: host lowercase · case 05
Reject malformed redirect authorities without interpreting path text as an authority: the host lowercase branch emits an incorrect decision.
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 ↗