sergehuber opened a new pull request, #38: URL: https://github.com/apache/unomi-tracker/pull/38
## Summary A new README section, "Deploying the website and Unomi": where Unomi can be compared with the website, and what that means for the profile cookie Unomi sets on its own host. - Behind a reverse proxy on the website's host (recommended), or on another host of the same domain: browsers keep the cookie. - On another domain: it is a third-party cookie. Safari blocks it, Chrome too in private windows or when the user blocks third-party cookies, and Firefox keeps a separate one per website. Unomi then sees the visitor as with `sendCredentials: false`: a new profile on each request with Unomi 4, a profile for the session with Unomi 2.x and 3.x. - The tracker copies the profile ID into its own cookie but does not send it to Unomi, so it cannot keep the profile itself yet (UNOMI-733). Documentation only. The test origins are all on localhost, which browsers treat as one site, so these cases are not covered by the tests yet (planned as a sub-task of UNOMI-1032). 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
