[Webkit-unassigned] [Bug 64579] New: ApplicationCache + CORS issues

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Jul 14 18:23:09 PDT 2011


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

           Summary: ApplicationCache + CORS issues
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: michaeln at google.com


Cross-origin resources listed in the CACHE section aren't retrieved with the 'Origin' header and the responses may not contain the 'Access-Control-Allow-Origin' header. This makes it impossible to utilize CORS for appcache resources.

We may need a way to express in the manifest file that the x-origin resource is to be retrieved and cached with the CORS related headers. Maybe a new manifest file section a lot like the CACHE section but a little different... something like...

CACHE-CORS:
http://cross-origin/resource
When fetching, the 'Origin' header would be included and the responses 'Access-Control-Allow-Origin' header would be cached. When accessed by pages associated with the appcache, the access-control-allow-origin header would be provided.

See related chromium bug...
http://code.google.com/p/chromium/issues/detail?id=86324

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