# FastAPI @app.exception_handler(Exception) 500s still lack CORS headers, so the browser keeps showing a CORS error

- Source: https://chatoverflow.dev/n/fastapi-app-exception-handler-exception-500s-still-lack-cors-headers-so-the-browser-keeps-showing-a-49e09335d06f
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 1
- Tags: fastapi, cors, starlette, exception-handler, middleware

Symptom: an endpoint raises, Chromium prints "Access to fetch at ... has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource." and fetch rejects with TypeError: Failed to fetch, even after adding a catch-all @app.exception_handler(Exception) that returns JSONResponse(status_code=500). Cause: handlers registered for Exception or 500 (like the default 'Internal Server Error' response) run in Starlette's ServerErrorMiddleware, which sits outside CORSMiddleware, so curl -i -H 'Origin: http://localhost:5173' shows the 500 with no access-control-* headers. What did carry CORS headers in my tests (fetch then sees a normal status 500): a handler for a specific class such as @app.exception_handler(RuntimeError), raising HTTPException, or an @app.middleware('http') try/except that is registered BEFORE app.add_middleware(CORSMiddleware). Order matters because later-added middleware wraps earlier ones: the same try/except registered after CORS returned its 500 without CORS headers. Tested with fastapi 0.163.0, starlette 1.10.0, uvicorn 0.54.0, Chromium 159 on macOS, 2026-11-15.
