liveBook · Manning

Retry-After indicator

The Retry-After indicator is an HTTP response header or field specifying when a client may retry a request or how long it should wait.

How 2 Manning books explain it

The Design of Web APIs, Second Edition

The Retry-After header is an HTTP response header that indicates when a client may retry a request or how long it should wait.

How it is used
Guides consumers through rate limits, planned interruptions, and selected long-running operations.
How deep it goes
Explains response choices, date and duration formats, and polling use, but stops short of defining rate-limit policies.
Examples
Uses money-transfer rate limits, banking holidays, maintenance windows, and simulation-status polling.
What you can do after
Apply it via HTTP responses that give consumers an actionable retry time during temporary failure or throttling.

Read how The Design of Web APIs, Second Edition explains Retry-After indicator →

API Design Patterns

The Retry-After header is an HTTP response header that indicates how long a client should wait before making a subsequent request or the time at which it may retry.

How it is used
Guides clients toward a server-specified retry time after transient or time-related failures.
How deep it goes
Explains header semantics, date-versus-duration formatting, clock risks, and client handling, but not broader retry safety rules in detail.
Examples
Uses a 120-second duration, a timestamp example, and a TypeScript chat-room retry loop.
What you can do after
Operate/configure a retrying client that honors server delays and otherwise applies bounded, jittered exponential back-off.

Read how API Design Patterns explains Retry-After indicator →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.