# Handle CHIPS (cookies having independent partitioned state) for embedding Ignition **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [November 26, 2024, 2:35pm UTC](https://forum.inductiveautomation.com/t/handle-chips-cookies-having-independent-partitioned-state-for-embedding-ignition/99122 "2024-11-26T14:35:53Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Magnus\_Henriksen](https://avatars.discourse-cdn.com/v4/letter/m/5daacb/32.png) [@Magnus\_Henriksen](https://forum.inductiveautomation.com/u/Magnus_Henriksen)\ **Post date:** [November 26, 2024, 2:35pm UTC](https://forum.inductiveautomation.com/t/handle-chips-cookies-having-independent-partitioned-state-for-embedding-ignition/99122/1 "2024-11-26T14:35:53Z")
Hi there! I'm experimenting with hosting webpages that embed ignition in an iframe. I tried doing the same as in [Ignition Perspective Tomcat X-Frame Options](https://forum.inductiveautomation.com/t/ignition-perspective-tomcat-x-frame-options/44524) and got a different message from the browser, that being `Cookie “JSESSIONID” has been rejected because it is foreign and does not have the “Partitioned“ attribute.` Turns out, the `Partitioned` attribute is going live now which means cookies from Ignition embedded in an iframe will be rejected due to not being explicitly declared as `Partitioned`. [Cookies Having Independent Partitioned State (CHIPS) - Privacy on the web | MDN](https://developer.mozilla.org/en-US/docs/Web/Privacy/Privacy_sandbox/Partitioned_cookies) I can get around this by using an older browser, or by turning off the feature in Firefox, or by making a proxy that rewrites the header, but long term I'd like to be able to supply this flag from Ignition itself. I could not find a header option that allowed me to simply add the `Partitioned` flag like I could with `Same-Site`, so I'm curious if anyone knows of a way to add this flag, or arbitrary text, to http headers from Ignition for the purpose of accepting embeds? (side note: anyone know if/when Ignition plans on moving from X-Frame-Options to Content Security Policy with `frame-ancestors`?)