'What is the proper long-term solution for the safari third-party cookie problem?
I've read a gazillion posts about the safari third party cookie problem and lots of kludgy workarounds that stop working as soon as the next version is released, but what I'm missing is what is supposed to be a sensible "best practice" solution.
I have a situation where app A on one domain needs to iFrame app B on another domain and app B needs a cookie purely to maintain state specific to that user. There's no tracking or anything cross-origin involved; the two apps don't share any cookies with each other or anyone else, so I don't really understand why what I'm doing is so dangerous.
At the moment the only option I can see is to use some kind of proxying to make the two apps appear to be on the same origin
Am I missing something?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|