Does Traefik Mesh provide built‑in request deduplication for retries to avoid duplicate writes?

Goal

Determine whether Traefik Mesh can be configured to prevent duplicate side‑effects when retrying requests that use non‑idempotent HTTP methods such as POST, PUT, or PATCH.

Constraints and uncertainty

Traefik Mesh relies on Traefik Proxy’s retry middleware, which retries based on attempt count and status codes but does not deduplicate requests. The mesh documentation advises using application‑level idempotency headers, yet there is an open discussion about adding built‑in idempotency support. It is unclear if a future release will provide request‑level deduplication or if users must continue to implement idempotency keys themselves.

Which approach should be taken to handle retries safely for non‑idempotent methods without relying on application‑level idempotency keys?