Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allowing SameSite=None Cookies in First-Party Sandboxed Contexts #450

Open
aamuley opened this issue Jan 16, 2025 · 0 comments
Open

Allowing SameSite=None Cookies in First-Party Sandboxed Contexts #450

aamuley opened this issue Jan 16, 2025 · 0 comments

Comments

@aamuley
Copy link

aamuley commented Jan 16, 2025

WebKittens

@annevk

Title of the proposal

Allowing SameSite=None Cookies in First-Party Sandboxed Contexts

URL to the spec

whatwg/html#10915

URL to the spec's repository

https://github.com/whatwg/html

Issue Tracker URL

No response

Explainer URL

https://github.com/explainers-by-googlers/csp-sandbox-allow-same-site-none-cookies

TAG Design Review URL

w3ctag/design-reviews#1004

Mozilla standards-positions issue URL

mozilla/standards-positions#1165

WebKit Bugzilla URL

No response

Radar URL

No response

Description

When third-party cookies (3PC) are blocked by Chrome and Firefox, contexts with the Content-Security-Policy: sandbox header or <iframe> sandbox attribute are no longer able to use SameSite=None cookies. The frame must include the allow-same-origin value to use cookies, which relaxes many security protections including the opaque origin.

We want to restore existing behavior and enable a frame to signal the browser to include SameSite=None cookies in first-party requests from sandboxed frames when 3PC restrictions are active with the allow-same-site-none-cookies value

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant