ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Safari’s Intelligent Tracking Prevention (ITP) caps third‑party cookie lifetimes and uses machine learning to block trackers. Learn how to spot the impact, avoid login breakage, and use the Storage Access API to keep your users happy.
Safari's ITP caps JavaScript-set cookies at 7 days, silently breaking analytics and sessions. Here's how the rule works, how to verify it, and why server-set cookies are the fix.
When Safari logs users out after navigation, ITP may block the auth cookie. This guide walks through detecting the issue, interpreting cookie attributes, applying fixes, and knowing when to file a WebKit bug.
Learn how Safari’s ITP 3.0 blocks third‑party cookies, why it matters for authentication, and how to adapt your app with token‑based auth and server‑side sessions.
Goal Design a strategy that ensures third‑party services can reliably access cookies and local storage after Safari’s Intelligent Tracking Prevention (ITP) interaction timer has elapsed. Constraints Safari partitions third‑party data until the user performs a qualifying top‑level interaction. The timer’s remaining duration is not exposed via any public JavaS
The goal is to maintain a cross‑site authentication flow that relies on a session cookie set on a third‑party domain (e.g., api.auth‑provider.com) while the user interacts with the main application (app.example.com). The cookie is set with SameSite=None to allow cross‑origin requests, and the server returns it over HTTPS. In local development the request ori
Integration boundary A web app embeds a cross-site authentication flow where a frontend on one origin sets SameSite=None; Secure cookies for an API on another. On localhost everything works: cookies are stored and sent as expected. Once deployed to production domains over HTTPS, Safari stops sending the cookies and the session appears lost. Constraints and u
safari