request fingerprint
A value, often a hash, calculated from the important parts of a request so the server can tell whether a repeated request is really the same one.
In more detail
It is stored with an idempotency key so that the same key sent with a different body is recognised as a conflict instead of being replayed. It usually covers the method, path and body, and ignores headers that change on every attempt.
Related terms
- idempotency key — A unique value a client sends with a non-idempotent request, such as a create, so the server can recognise a retry and return the original result instead of acting twice.
- hash — A short fixed-length fingerprint calculated from data, which changes completely if even one byte of the data changes.
- 409 Conflict — The HTTP status meaning the request conflicts with the current state of the resource.
Taught in
- Idempotency Keys — Modern API Architecture: REST, GraphQL & gRPC
- Idempotency, And Exactly Once As A Fiction — Scalable System Design & Distributed Architecture