Allow 'chrome-extension:' URLs to bypass content settings (1/2)
We changed the behavior of 'Document::firstPartyForCookies' to return an empty URL in the case where any URL in the ancestor chain doesn't match the current document's URL. Previously, we'd simply return the top-level document's URL. This means that the content-settings bypass check in 'ContentSettingsObserver::IsWhitelistedForContentSettings' sees an empty URL as opposed to a 'chrome-extension://' URL for cases in which an extension loads a resource, so content settings are applied as per usual. This breaks things fairly badly for folks who have turned on third-party cookie blocking. In these patches, we introduce a new scheme registry for those schemes which ought to override Blink's concept of "first-party" when they're loaded into the top-level browsing context. Patch 1 (Blink): [This patch] Patch 2 (Chromium): https://codereview.chromium.org/1332563006 BUG=527963 R=jochen@chromium.org Review URL: https://codereview.chromium.org/1305253012 git-svn-id: svn://svn.chromium.org/blink/trunk@201964 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Showing
Please register or sign in to comment