Expand description
Optional server-side replay tracking.
created already bounds how long a captured request stays valid. A replay guard additionally
refuses a second use of the same request inside that window, at the cost of a store on the
request path. Whether that is worth it depends on the route: a request whose effect can be
repeated needs one, a request that only opens a session usually does not.
Structs§
- InMemory
Replay Guard - A process-local replay guard for tests and low-traffic, single-replica services.
Traits§
- Replay
Guard - Records verified requests so that each is accepted once.