2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
set: 4
|
|
|
|
|
code: 405
|
|
|
|
|
title: Method Not Allowed
|
2015-11-07 05:34:40 +01:00
|
|
|
references:
|
|
|
|
|
"Rails HTTP Status Symbol": ":method_not_allowed"
|
2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
|
2015-11-07 06:45:46 +01:00
|
|
|
The 405 Method Not Allowed status code indicates that the method received in
|
2015-11-07 05:34:40 +01:00
|
|
|
the request-line is known by the origin server but not supported by the target
|
2015-11-07 06:45:46 +01:00
|
|
|
resource.
|
|
|
|
|
|
|
|
|
|
The origin server MUST generate an Allow header field in a 405 response
|
|
|
|
|
containing a list of the target resource's currently supported methods.
|
2015-11-07 05:34:40 +01:00
|
|
|
|
|
|
|
|
A 405 response is cacheable by default; i.e., unless otherwise indicated by the
|
|
|
|
|
method definition or explicit cache controls (see [Section 4.2.2 of RFC7234][2]).
|
|
|
|
|
|
|
|
|
|
Source: [RFC7231 Section 6.5.5][1]
|
|
|
|
|
|
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc7231#section-6.5.5>
|
|
|
|
|
[2]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
|
