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

Changing recommendation for using CORS for cookies in A>B>A embeds #10

Open
DCtheTall opened this issue Apr 16, 2024 · 0 comments
Open

Comments

@DCtheTall
Copy link
Member

In the explainer section on A>B>A embeds, one possible solution we proposed was to allow A>B>A embeds to use CORS to regain cookie access without needing to call the Request Storage Access API.

After thinking about this more and discussing with our team, we have decided that CORS is not the right solution for A>B>A embeds that need an HTTP-only solution to restore cookie access. Our main line of reasoning is that requests opted into CORS still send credentials by default before the site has a chance to reveal to the browser whether the context sending cookies is acceptable. In particular, this can cause a problem for cross-site POST requests which may have side effects on the server side before they can tell the browser not to send cookies.

A more favorable solution for this use case is the Request Storage Access headers proposal which offers a mechanism in which will not send cookies to the site until it has explicitly opted into doing so in that particular context.

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