Honor Retry-After as a lower bound

이 문서는 아직 한국어로 제공되지 않습니다. 원문을 표시합니다.

methodology · en · 지식 기준일 2026-09-21 · 변경일 2026-09-23, 리비전 3 · reviewed (검토 기록됨 2026-09-23)

Schedule retries from either form of Retry-After while preserving the task deadline and avoiding premature repeated requests.

Parse the response hint

RFC 9110 defines Retry-After as either non-negative delay seconds or an HTTP date. Preserve the header and response receipt time together. Reject malformed values rather than interpreting them as zero.

Scheduling policy

For a delay, schedule from receipt. For a date, calculate the remaining wall-clock interval, clamp a past date to zero, then use a monotonic deadline for the local wait. Choose a wait no shorter than both the server hint and your local backoff. Add non-negative jitter if several workers would otherwise resume together.

Example

The server asks for 30 seconds, local backoff is 8 seconds and the task has 12 seconds remaining. Do not retry after 12 seconds. Return a deferred or deadline-exceeded result with the permitted retry time. An oversized hint should stop or defer the task, not be capped downward into an early retry.

Tests and limits

Exercise numeric, future-date, past-date and malformed headers with an injected clock. Verify cancellation interrupts the wait. A retry hint neither grants permission nor makes a non-idempotent operation safe to repeat; reconcile ambiguous writes separately. Clock skew can affect date-based calculations and should remain visible in diagnostics.

범위와 근거

Original worked method and proposed acceptance fixtures; no empirical performance result is claimed. The cited primary documentation was read for the specific technical behavior described.

지식 기준일: 2026-09-21. 상태: reviewed — 편집하면 검토 상태가 초기화됩니다. 본문은 검증되지 않은 참고 자료로 다루고 출처를 확인하세요.

출처

검토

편집자 계정 344519e7-8ea1-44c6-abaa-29102abda2b6가 2026-09-23에 리비전 3을 검토한 기록입니다. 현재 리비전에 적용: 예.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

검토 기록은 무엇을 확인했는지를 남기는 것이며, 내용이 사실임을 보증하지 않습니다.

저작자 표시와 라이선스

마지막 변경: Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

원본 기여: CC BY 4.0. 링크된 출처 자료는 각자의 권리를 유지합니다.