[Webkit-unassigned] [Bug 63090] img.crossOrigin not respected on cached images
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Jun 21 14:02:32 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=63090
Kenneth Russell <kbr at google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |abarth at webkit.org,
| |ap at webkit.org,
| |japhet at chromium.org
Ever Confirmed|0 |1
--- Comment #1 from Kenneth Russell <kbr at google.com> 2011-06-21 14:02:32 PST ---
It seems that the CORS state of the resource needs to be incorporated into the cache's key.
Clearly, if the resource is initially fetched without CORS, and then a CORS request is made for the same resource, the second fetch should not hit in the cache.
However, if the resource is initially fetched with a CORS request, and then a subsequent fetch of the resource is made, it isn't clear to me whether we should (a) hit in the cache, (b) re-fetch the resource, or (c) hit in the cache, but in the returned reference to the resource, indicate that any CORS permissions should be ignored for this request.
--
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