- From: Rakina Zata Amni <notifications@github.com>
- Date: Mon, 01 Dec 2025 04:03:35 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/issues/1838/3596160755@github.com>
rakina left a comment (whatwg/fetch#1838) We discussed this proposal during a joint WHATWG - WebPerf session last month, see [minutes](https://www.w3.org/2025/11/13-whatwg-minutes.html) (search for "fetch retry"). I think most people are supportive to have an API for this, and agreed on the general design in the [proposal](https://github.com/explainers-by-googlers/fetch-retry/blob/main/README.md). Some important details: - Sending `Retry-Attempts` header on CORS requests without preflight is likely OK, with 2 conditions: We don't allow the API in `no-cors` mode, and we need to confirm with the IETF folks about whether there's any conflict with their `Idempotency-Key` proposal. As @fergald noted above, I think that only conflicts with `Retry-GUID`, which we have removed from this proposal. I can also confirm this in a more IETF-specific space if needed. - `retryNonIdempotent` can be useful? I think there are some opinions on this although I don't think it's clearly captured in the minutes, but personally it's fine if we need to drop this for V1. - `retryIfServerUnreached` is likely useful, and some browsers already implement this automatically. - New option `retryFromLastRedirectHop` is also likely useful, to reduce load and increase cases covered by `retryIfServerUnreached`. - Retrying HTTP errors can be dropped from v1. There's no strong need for this currently. So for the V1, I think just having the original proposal as is from the current [explainer](https://github.com/explainers-by-googlers/fetch-retry/blob/main/README.md) that is currently running in an Origin Trial from Chrome + getting `Retry-Attempts` header clarified with IETF should hopefully be enough and we can start working on specs soon? LMK if there are more things to do before that :) -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1838#issuecomment-3596160755 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1838/3596160755@github.com>
Received on Monday, 1 December 2025 12:03:39 UTC