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 OAuth2 Flow Pitfalls: A Real-World Case Study

A lot of CORS bugs are really OAuth2 architecture bugs wearing a fake mustache. I’ve seen teams spend days tweaking Access-Control-Allow-Origin headers when the real problem was simpler: they were trying to run the wrong OAuth2 flow in the browser, or they expected the browser to carry cookies and tokens across origins in ways it never will. Here’s a case study based on a very normal setup: frontend: https://app.example.com API: https://api.example.com auth server: https://auth.example.com The team had a React SPA talking directly to the API. They wanted users to click “Login with OAuth”, get redirected to the auth server, come back with a session, and then call the API with fetch(). ...

March 30, 2026 · 6 min · headertest.com