405
Method Not Allowed
The HTTP method used in the request (GET, POST, PUT, DELETE, etc.) is not supported for the target resource. The server knows the resource exists but rejects the specific method.
What does HTTP 405 mean?
The HTTP method used in the request (GET, POST, PUT, DELETE, etc.) is not supported for the target resource. The server knows the resource exists but rejects the specific method.
Common causes
- 1
Sending a POST request to an endpoint that only accepts GET, or vice versa. The API supports the URL but not with that method.
- 2
A form submission uses GET instead of POST, or the frontend sends the wrong method due to a misconfigured fetch/axios call.
- 3
The server or framework has CORS preflight (OPTIONS) misconfigured, and the actual request method is being rejected.
How to fix it
- 1
Check the Allow header in the response — it lists which HTTP methods the endpoint accepts. Switch to a supported method.
- 2
Review your API documentation to confirm the correct method for each endpoint. REST conventions: GET to read, POST to create, PUT/PATCH to update, DELETE to remove.
- 3
If OPTIONS requests fail, ensure your server handles CORS preflight correctly and lists the required methods in Access-Control-Allow-Methods.
Monitor for HTTP 405 errors
Uptrack sends GET requests by default to check endpoint availability. If your health check endpoint only accepts POST, configure the monitor with the correct HTTP method to avoid false 405 alerts.
Catch HTTP errors before your users do
20 monitors free — 10 at 30s, 10 at 1min. No credit card required.
Start Monitoring Free