[kisstheblade]

> ⁇ If the server returned 404, the server returned 404. This means the client application/the user agent made a mistake, indicated by the leading digit 4.

Or the endpoint wasn't configured properly even though the client had the right address. Happens often when developing, maybe another developer changed the endpoint url? Or in production some endpoint hasn't started. (yes this problem is seldom a problem in production or you usually know from other things that the problem is at the server, annoying still)

I've had problems with not knowing if 404 is "person not found" type error or "endpoint address is plain wrong"

"Bad Request" doesn't describe the situation either very well, I've used it myself to eg. signal missing mandatory parameters.

But just using eg. the code 200 as someone suggested and returning your own status message seems a little bit overkill.