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

Support for Partitioned cookie attribute (AKA CHIPS) / make cookies more flexibel #12480

Open
mkurz opened this issue Mar 15, 2024 Discussed in #12357 · 1 comment
Open

Support for Partitioned cookie attribute (AKA CHIPS) / make cookies more flexibel #12480

mkurz opened this issue Mar 15, 2024 Discussed in #12357 · 1 comment

Comments

@mkurz
Copy link
Member

mkurz commented Mar 15, 2024

Discussed in https://github.com/orgs/playframework/discussions/12357

Originally posted by jdf200 February 16, 2024
I have recently been checking our Play app's compliance with the upcoming change Google is planning to block 3rd party cookies / partition those cookies to the top level domain.

We have an application that is embedded within a site as an iframe on a different top level domain which needs to set cookies, however under Googles proposed model (CHIPS) we will need to add a 'Partitioned' attribute to the Set-Cookie header.

I've checked the Play documentation and implementation and I cannot see any simple way of adding this in the current model.

I have implemented a workaround by injecting a overridden version of the CookieHeaderEncoding class into my application, however this is not ideal.

Are there any plans to add this flag to the Cookie class / configuration in an upcoming release? Or is there a cleaner way to add additional flags to the Set-Cookie response?

@mkurz mkurz added this to the 2.10.0 / 3.1.0 milestone Mar 15, 2024
@mkurz
Copy link
Member Author

mkurz commented Mar 15, 2024

See my comments in the original discussion:

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

No branches or pull requests

1 participant