New issue
Advanced search Search tips

Issue 910711 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 910720

Blocking:
issue 910708



Sign in to add a comment

SplitCache: Support opaque top-frame origins

Project Member Reported by jkarlin@chromium.org, Nov 30

Issue description

See 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.
 
Blocking: 910708
Status: Available (was: Untriaged)
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.

Comment 4 by cammie@google.com, Jan 16 (6 days ago)

Blockedon: 910720

Sign in to add a comment