Purpose, sources & privacy
A learning tool with visible boundaries.
Why this playground exists.
Request Replay Lab makes a few software failure modes small enough to inspect. The examples use invented jobs, request identifiers and version numbers. A trace is a demonstration of the selected toy rule, with its assumptions documented alongside it.
The site provides educational exercises without accounts, subscriptions, advertising or a service-order form. It makes no claim of production testing, client results or independent technical review.
Sources and context.
- Making retries safe with idempotent APIs
AWS Builders Library: request identity, atomic recording and repeated intent.
- HTTP request methods
MDN: method safety and idempotency semantics.
- HTTP caching
MDN: freshness and validation for HTTP caches.
- Software architecture and integration context at Pharos Production
An industry reference for the application domain. It is not evidence for the synthetic results shown here.
Sources checked . The event-order and record-copy examples state their own rules rather than claiming to reproduce a particular vendor's system.
What happens to your selections.
The experiments run in the current browser tab. Controls change local example state; they do not send requests, write to browser storage or collect contact information. Reloading restores the default examples.
The site adds no analytics or advertising cookies. Its hosting provider processes the ordinary network information needed to serve pages. External source links lead to websites with their own privacy practices.