SplitCache: Support opaque top-frame origins |
|||
Issue descriptionSee WebContentsSplitCacheBrowserTest.SplitCache and how it has a data: url that doesn't get split in the cache because the opaque origin stringifys to "null" instead of a random sequence of characters. We can either not cache resources with opaque top frame origins or we'll need to generate a nonce for the origin on the renderer and make sure it plumbs up to TopFrameOrigin.
,
Nov 30
,
Dec 6
I'm voting for not caching resources when the top frame origin is opaque. When else would we get to use these resources? Blink's memory cache should take care of reusing resources within the current page load.
,
Jan 16
(6 days ago)
|
|||
►
Sign in to add a comment |
|||
Comment 1 by jkarlin@chromium.org
, Nov 30