80334 2012-03-05 15:11:01 -0800 Refine CachedRawResource reuse based on request headers 2012-04-16 17:22:51 -0700 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED P2 Normal --- 1 japhet japhet abarth ap koivisto simonmorris oldest_to_newest 571081 0 japhet 2012-03-05 15:11:01 -0800 So far, I've fixed http://trac.webkit.org/changeset/108576, which was allowing CachedResource re-use when the two requests' Range headers weren't identical. There are other, similar cases, where headers need to be the same (e.g., "Authorization" was recently pointed out to me). I'm debating whether to continue the whack-a-mole game of finding and fixing these headers that need to match to be cahceable. The alternative is to switch to requiring all headers to match except for a whitelist (e.g., I'm pretty sure we still want a cache hit even if the referrers don't match). Thoughts are appreciated. 603609 1 japhet 2012-04-16 17:22:51 -0700 This should have been resolved by http://trac.webkit.org/changeset/110608