[Webkit-unassigned] [Bug 125151] New: Scripts loaded with yepnope.js are not cached

[bugzilla-daemon at webkit.org]

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

           Summary: Scripts loaded with yepnope.js are not cached
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh
        OS/Version: Mac OS X 10.9
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Page Loading
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jonathan.abourbih at blackboard.com


If a script is loaded via yepnope.js, even if appropriate cache-control headers are sent by the server, Webkit does not cache the response. This causes all scripts loaded with yepnope.js to download twice.

Actual behaviour: Scripts downloaded over SSL with yepnope.js are loaded twice, and are not cached, despite a long max-age header from the server.

Expected behaviour: Once a script has been downloaded, and the server has sent an appropriate cache-control header, the script should not be downloaded again.

Steps to reproduce:
1. Open the Web Inspector and begin recording a timeline.
2. Go to http://jsbin.com/ocuxum/6
3. Observe in the timeline that jquery.js (downloaded from Cloudflare) is downloaded twice, and the "Cached" column says "No".
4. Click "Refresh" to reload the page.
5. Observe that the "Cached" column still says "No" for jquery.js. Expected result is that it should say "Yes" and should not download again.

Note that a related issue has been logged with the yepnope.js project: https://github.com/SlexAxton/yepnope.js/issues/173.

Some background: Yepnope.js inserts an image tag in the page with the script URL to "prime" the cache with the scripts. Once the scripts have been downloaded, it then inserts <script> tags in the page in the appropriate order of execution.

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