Return 405 Method Not Allowed for unimplemented HTTP methods

[ramsey]

Consider returning 405 Method Not Allowed when the route exists but the requested HTTP method is not implemented for the route. An Allow header must also be included that lists the implemented/allowed methods. See http://tools.ietf.org/html/rfc2616#section-10.4.6.

[augustohp]

This could be handled a lot like issue #18. I just haven't put much thought to it yet, but we could do it in a lot of ways:

• Just throw an RestHttpException with the error code and let the user deal with it
• Do something like what is proposed in Default "not found" route. #18, implement a Route with it

Despite not being the greatest fan of a pre-declared route for 404, 405 and so on; this is the most straight-forward solution I can think of.

[augustohp]

Missing the Allow part in the header. I couldn't find a good way of finding all the available methods on the route in a way I didn't feel like ripping my head off (traversing through all the routes again).

@alganet: is there some simple and nice way to do that? Otherwise just a cherry-pick here should do, after ripping my head off, of course.

[ramsey]

Great stuff!