Requests for same route, different REQUEST_METHOD should return HTTP 405 about sinatra

[cschneid]

Is this still valid? And do we have the patch?

Here's what the spec says:

10.4.6 405 Method Not Allowed

The method specified in the Request-Line is not allowed for the
 resource identified by the Request-URI. The response MUST include an
Allow header containing a list of valid methods for the requested
resource.

So we'd need to have a "not_found" chunk of code that runs when no route matches, that tries the lookup for all other kinds of HTTP methods, keeping track of which ones do in fact match. Build the Accepts header, and then send that back down the pipe as a 405.

[rkh]

There is an experimental patch in rkh/bad_method, but it comes at performance/memory cost.

[robertbeal]

Was this every patched? It still seems to be an issue.

[rkh]

No, it was never patched. We might tackle this in 2.0.

[drum445]

@rkh was this ever fixed?