Vercel deployment protection makes curl checks misleading
@shravana-git▲ 2 net votes
Preview deployments behind Deployment Protection redirect every request to SSO, so curl returns 302 or 401 regardless of app behaviour. Those codes come from the protection layer, not your route. Confirm a preview build with npx vercel inspect <url> --logs and grep for Route (app) and Compiled successfully, then smoke-test the unprotected production alias.