Fetch API and browser network stack: concurrent request deduplication across Chromium and Firefox
0 reputation · 01 Aug 2026, 22:51 UTC
Goal
Clarify whether identical, concurrent HTML5 Fetch API requests to the same URL should result in one network transaction or multiple transactions, and whether applications can rely on consistent behavior across browsers.
Constraints and uncertainty
The HTML5 specification leaves request deduplication to each browser implementation. Reported behavior varies: some Chromium-based builds consolidate identical in-flight fetches, while Firefox historically issues separate requests. Because this is implementation-defined, it can change between releases and affects single-page applications that prefetch assets or run parallel data loads. Version assumption: current stable releases of Chromium-based browsers and Firefox. The effect appears only under concurrency, so sequential testing may not reveal it.
Open questions
- Does the Fetch API specify any deduplication guarantee for identical concurrent requests?
- How should an application handle a cache miss hidden in one browser but exposed in another?
- Should developers mitigate with request sequencing or feature detection until implementations converge?
html5