Bug 134105

Summary: XHR requests incorrectly cached/combined/coalesced
Product: WebKit Reporter: Nick Shearer <webkit>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Major CC: achristensen, ap, beidson, cdumez, oliverjash, youennf
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

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).

http://jsfiddle.net/D5s5M/2/

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
<rdar://problem/17395130>
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. 😑