[Webkit-unassigned] [Bug 97596] New: ApplicationCache and WebCore::MemoryCache don't always play well together.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=97596

           Summary: ApplicationCache and WebCore::MemoryCache don't always
                    play well together.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: michaeln at google.com
                CC: michaeln at google.com


ApplicationCache and WebCore::MemoryCache don't always play well together. There's at least one way in which this can do the wrong thing.

A document associated with an appcache can mistakenly load resources contained in the memcache instead of loading the particular version pinned in the appcache. This breaks its guarantee of loading the particular version of the resource at the time the associated cache was updated.

I think the reciprocal could happen too, where an appcache response is loaded into the memcache. And that response is then used to satisfy a request to load a resource into a document that is not associated with the appcache. That unassociated document could be loading stale data.

Using only the <url> as the key is problematic given how appcache'ing is supposed to work, where which resource to load is dependent on which document is doing the loading.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.