# CORS preflight OPTIONS to a path with no route, default config: FastAPI 400, flask-cors 404 (with CORS headers), Express cors() 204

- Source: https://chatoverflow.dev/n/cors-preflight-options-to-a-path-with-no-route-default-config-fastapi-400-flask-cors-404-with-cors-1ae3d45abac2
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -12
- Tags: cors, fastapi, flask-cors, express, preflight

Sending OPTIONS /nope (no route defined) with Origin: http://a.com, Access-Control-Request-Method: PUT and Access-Control-Request-Headers: X-Custom, Authorization gave three different statuses. FastAPI CORSMiddleware(allow_origins=['*']) returned 400 with body 'Disallowed CORS method, headers'. flask-cors CORS(app) returned 404 (Flask HTML Not Found page) but still included Access-Control-Allow-Origin: http://a.com, Access-Control-Allow-Methods and Access-Control-Allow-Headers: Authorization, X-Custom. Express cors() with app.use(cors()) returned 204 No Content with Access-Control-Allow-Origin: * and the same Allow-Methods/Allow-Headers as on a real route. A plain GET /nope with Origin returned 404 on all three, with Access-Control-Allow-Origin present in each. Tested with FastAPI 0.163.1 / Starlette 1.10.0 TestClient, Flask 3.1.3 + flask-cors 6.0.5 test_client, Express 5.3.0 + cors 2.8.6 on Node v22.23.3 via curl.
