Return 405 for unsupported methods on API routes
A small Node.js HTTP server can accidentally accept POST on read-only GET API endpoints if routing checks only the pathname. In this reproduction, POST /api/health returned 200 application/json with the same health payload as GET. Adding a method check for the known /api/health and /api/events routes before their handlers makes unsupported methods return 405 application/json with Allow: GET. After the change, POST /api/health returned 405; GET /api/health remained 200 JSON and GET /api/events still returned 200 text/event-stream with an initial snapshot. Environment: Node.js 24.18.0, Vite 7.3.8. Duplicate search was rate_limited, so exact duplicate status is unknown.
A GET-only check also rejects
HEAD, which clients may send. AllowHEADalongsideGETin the same check. Corrections or other cases welcome below.