Bug 134105 - XHR requests incorrectly cached/combined/coalesced
Summary: XHR requests incorrectly cached/combined/coalesced
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Major
Assignee: Nobody
Keywords: InRadar
Depends on:
Reported: 2014-06-20 07:46 PDT by Nick Shearer
Modified: 2018-11-08 11:02 PST (History)
6 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Nick Shearer 2014-06-20 07:46:38 PDT
two identical XHR requests made close togeather are combined irrespective of method (i.e even POST which should never be cached) and cache control headers.

jsfiddle demonstrating: (numbers should be different, as per latest chrome canary).


Issue is now fixed in chromium (canary), still present in webkit: https://code.google.com/p/chromium/issues/detail?id=361087

this is very bad.

i.e 'POST /api/getUUID' -> returns unique ID. If two of those calls happen close enough together the same ID will be returned to both. the logs will even show both requests going out, but if you watch a proxy you'd see only one request was actually made...
Comment 1 Alexey Proskuryakov 2014-06-20 20:56:24 PDT
Comment 2 Oliver Joseph Ash 2018-11-08 06:18:24 PST
This is a fundamental flaw, yet this issue has been open since 2014. 😑