root@hack3rs:/srv/www$ curl -i /405/
HTTP/1.1 405 Method Not Allowed
The endpoint exists but does not accept this HTTP method.
status-summary.log
HTTP 405 Method Not Allowed
The route is valid but the server rejected the HTTP method — for example, a POST sent to a GET-only endpoint.
This is almost always a client integration mistake. Compare the method you are sending against what the endpoint contract specifies.
likely-causes.lst
- $POST, PUT, or DELETE sent to a read-only route.
- $Form submission points to an endpoint that only handles GET.
- $A proxy or middleware strips method-override headers.
- $OPTIONS preflight or CORS configuration is broken for browser requests.
recovery-steps.md
- Check the allowed methods in the API documentation or route definition.
- Retry with the correct HTTP method and matching payload format.
- Inspect proxy and CDN configuration for method filtering.
- Validate OPTIONS handling and CORS headers for browser-originated requests.
quick-actions.sh
ops-note.txt
Use these pages for debugging and user guidance. In production, configure your host or reverse proxy to return the matching HTTP status code for the route (especially for 405 and 404/500 responses) rather than serving a 200 with error-themed content.