HTTP 405 Method Not Allowed

What the 405 Status Code Means

The HTTP 405 Method Not Allowed status code indicates that the server received the request and recognized the target resource, but the HTTP method used in the request is not supported for that resource.

In other words, the URL exists, but the request method such as POST, PUT, or DELETE is not allowed for the requested endpoint.

Common Causes of HTTP 405 Errors

• Sending a POST request to a read-only endpoint
• Using GET when the API requires POST
• Incorrect routing configuration in web frameworks
• Server restrictions on specific HTTP methods
• Security filters blocking unsafe methods

Example of a 405 Response

HTTP/1.1 405 Method Not Allowed
Allow: GET, HEAD
Content-Type: text/html

Servers often include an Allow header which lists the HTTP methods supported by the requested resource.

Common HTTP Methods

• GET – retrieve a resource
• POST – submit data to the server
• PUT – replace a resource
• PATCH – partially update a resource
• DELETE – remove a resource

If a client sends a method that is not supported for a particular resource, the server may return a 405 response.

How Developers Diagnose 405 Errors

• Check the HTTP method used in the request
• Review API documentation
• Inspect server routing configuration
• Verify allowed methods for the endpoint

Related HTTP Status Codes

• 400 Bad Request
• 401 Unauthorized
• 403 Forbidden
• 404 Not Found
• 405 Method Not Allowed
• 408 Request Timeout
• 409 Conflict
• 410 Gone
• 415 Unsupported Media Type
• 418 I'm a teapot
• 422 Unprocessable Entity
• 429 Too Many Requests
• 451 Unavailable For Legal Reasons
• 500 Internal Server Error
• 502 Bad Gateway
• 503 Service Unavailable
• 504 Gateway Timeout

Summary

The HTTP 405 Method Not Allowed status code indicates that the server understands the request but does not allow the HTTP method used for the requested resource.

Ensuring that clients use the correct HTTP methods for each endpoint is essential when designing REST APIs and web services.