405 for wrong method instead of 404

Is it possible to have 405 (Method Not Allowed) returned in reply to existing url, which was called with a wrong method (e.g. GET instead of POST)?
Currently, express returns 404 (Not Found) for existing url, called with a wrong method, and, it is sort of misleading in debugging.

[defunctzombie]

This would be up to you to implement. Because of the myriad of ways you can specify routes in express it cannot really know if the same route exists with a similar method.

[dougwilson]

@defunctzombie I normally would agree, but because express always responds to OPTIONS requests automatically (https://github.com/visionmedia/express/blob/master/lib/router/index.js#L133) it almost seems like if options.length > 0 by the time the router is ready to 404, it could 405 instead?

[defunctzombie]

@dougwilson It actually doesn't respond to options correctly. If I make a second router with different methods for the same routes, none of those will be caught by the options response feature in the first router. The 404 does not come from a router, it happens because the middleware processing fell through to some handler that responded with a 404 (often well outside the router). We would need some sort of sentinel property on the request/response object to indicate to the default 404 handler that there was a possibility of handling the request.

[dougwilson]

Right, I didn't say it responded correctly :) We should have probably put it behind an option that was off by default.