Skip to content

Fetch retry (draft)#1923

Draft
noamr wants to merge 4 commits into
whatwg:mainfrom
noamr:retry
Draft

Fetch retry (draft)#1923
noamr wants to merge 4 commits into
whatwg:mainfrom
noamr:retry

Conversation

@noamr
Copy link
Copy Markdown
Contributor

@noamr noamr commented Apr 20, 2026

  • At least two implementers are interested (and none opposed):
  • Tests are written and can be reviewed and commented upon at:
  • Implementation bugs are filed:
    • Chromium: …
    • Gecko: …
    • WebKit: …
    • Deno (not for CORS changes): …
  • MDN issue is filed: …
  • The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)


Preview | Diff

@noamr noamr marked this pull request as draft April 20, 2026 13:25
@issacgerges
Copy link
Copy Markdown

👋🏼 Know this is early days but some things I think would be valuable here

  • Ability to specify jitter, and maybe a maxDelay clamp (e.g. retry 4×, but stop growing the delay past some ceiling)
  • Customizable or standardized retry conditions
    • I could imagine folks will want to retry or not based on specific status code (429/503/5xx) not sure if this is consumer specific or can just be generic
  • Honoring Retry-After so client backoff doesn't fight the backend
  • A way to observe retries (I can imagine its a useful alertable metric)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants