[Webkit-unassigned] [Bug 80439] New: Race condition in handling non-cachable resources.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Mar 6 12:59:51 PST 2012


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

           Summary: Race condition in handling non-cachable resources.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
               URL: http://examples.nfshost.com/nocacherace/result1/index.
                    html
        OS/Version: Unspecified
            Status: NEW
          Keywords: InChromiumBugs
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: bkuhn at google.com


Originally filed as a Chrome bug:
http://code.google.com/p/chromium/issues/detail?id=116988


Chrome Version       : 18.0.1025.39
OS Version: 
URLs (if applicable) : http://examples.nfshost.com/nocacherace/result1/index.html http://examples.nfshost.com/nocacherace/result2/index.html


Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: FAIL
    Firefox 9: OK
         IE 9: OK

What steps will reproduce the problem?
Visit a page that loads a non-cachable script and an iframe that also uses that script.  The unexpected behavior happens if the iframe loads before the script finishes loading.

What is the expected result?
The main page and the iframe should get different copies of the non-cachable script, which is exactly what happens in all other cases.

What happens instead?
The script in the iframe is not requested; instead the copy from the main page is used. If this were to always happen, fine. But it only happens if the iframe is parsed while the script on the main page is mid-download. It seems like Chrome is assuming that the mid-download resource is cachable.


Please provide any additional information below. Attach a screenshot if
possible.

Please see the test cases I've developed to demonstrate the problem:
http://examples.nfshost.com/nocacherace/result1/index.html
http://examples.nfshost.com/nocacherace/result2/index.html


UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.39 Safari/535.19

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



More information about the webkit-unassigned mailing list