Skip to content
Networking·Intermediate·Conceptual·1 min read

What is the practical risk of a client automatically retrying a timed-out POST?

Short interview answer

If the original request actually reached the server and succeeded before the timeout, an automatic retry can create a duplicate resource or trigger the action twice, since POST has no idempotency guarantee to fall back on.

Key takeaway

Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.

← Back to HTTP methods, status codes, and idempotency

Related questions