CORS and Safari Quirks: ITP Mistakes and Fixes

Safari is where “my CORS setup is fine” goes to die. I’ve seen teams burn hours staring at Access-Control-Allow-Origin headers while the real problem was Safari’s privacy model, cookie policy, or a cross-site storage assumption that worked everywhere else. If you build anything involving frontend apps, APIs, auth, embedded widgets, or third-party dashboards, you need to treat Safari as a separate threat model and a separate testing target. CORS is only one layer. Safari’s Intelligent Tracking Prevention (ITP) changes the behavior around cookies, storage, and cross-site identity, which means a request can be perfectly valid from a CORS perspective and still fail in practice. ...

November 2, 2026 · 7 min · headertest.com

CORS Case Study: same-site vs same-origin confusion

A lot of CORS bugs are not really CORS bugs. They’re architecture bugs caused by mixing up same-origin and same-site, then trying to patch the fallout with headers until the browser stops complaining. I’ve seen this play out the same way more than once: frontend on app.example.com API on api.example.com session cookie involved somebody says “it’s the same domain, so it should work” someone else adds Access-Control-Allow-Origin: * auth breaks, or worse, security assumptions break Here’s a real-world style case study that shows how teams end up here, what the browser is actually doing, and what the fix looks like. ...

October 16, 2026 · 7 min · headertest.com

CORS in Laravel Sanctum SPA Authentication

Laravel Sanctum SPA auth looks simple on paper: frontend hits /sanctum/csrf-cookie, then logs in, then sends session cookies with future API requests. The part that trips people up is CORS. Not because CORS is complicated in theory, but because Sanctum relies on cookies + CSRF + stateful requests, and browsers get very picky when credentials are involved. If your React, Vue, or Nuxt frontend lives on http://localhost:5173 and your Laravel API lives on http://localhost:8000, you’re in CORS territory immediately. ...

October 8, 2026 · 6 min · headertest.com

CORS and Auth Tokens: JWT vs Cookies

CORS gets messy the moment authentication enters the picture. A simple public GET with Access-Control-Allow-Origin: * is easy. GitHub’s API does exactly that for many responses: access-control-allow-origin: * access-control-expose-headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset, Warning That works because a browser can fetch public data without credentials. The moment you send cookies or an Authorization header, the rules change. ...

October 4, 2026 · 6 min · headertest.com

CORS for Headless CMS Preview Without the Headaches

Headless CMS preview sounds simple until the browser gets involved. Your editor clicks “Preview draft”, your frontend tries to fetch unpublished content from a CMS API on another origin, and suddenly the browser throws a CORS error that says almost nothing useful. I’ve seen teams lose hours here because they treated preview like normal production API traffic. It isn’t. Preview usually combines the hardest parts of cross-origin browser security in one flow: ...

June 17, 2026 · 7 min · headertest.com