404 Not Found has not been implemented about express-api-es6-starter HOT 4 CLOSED

I changed it to 405. I have found people use Method Not Allowed when there is no resource/route for something.

Most people seem (at least beginners) to confuse themselves of 'Resource being not found' when 404 is shown. 405 is more meaningful for cases like those. Yes, we can use 404 and replace it with a message like Route not found because only having a message like Not found causes some confusion.

from express-api-es6-starter.

And yes, I've kept the notFoundError method as it is.

from express-api-es6-starter.

So we show 404 when there is actually an unavailable resource (like /users/12133213), but use 405 for a non-existent route?

from express-api-es6-starter.

Correct.

from express-api-es6-starter.