@w0stn0@Hexalyse@thecto@achesui_@kartik_builds Yep, and ever since the other team at work decided 404 means no results I've been stuck catching exceptions instead of handling responses
@Hexalyse@thecto@achesui_@kartik_builds For a restful api 404 isn't an error it literally means not found. So for a search endpoint with no results the restful convention would return a 404. Personally i prefer 204 no content but if you talk to any restful Bros, they'll swear up and down that 404 is the right response
@thecto@achesui_@kartik_builds If you are making an api call to see if a username is already in use, 404 not found means congratulation the user is free to create this account nobody else has taken it yet, 404 in this case is not an error because a the server is missing an html/js file.
@thecto reply to everything with a 200ok, and embed the errors inside the payload. For the older .net framework http libraries that wasn't actually the worst idea since the client would throw an exception for all 400+ http status codes. and coworkers doing restful api's insisted on 404's
If snap isn't happening next month, it's an opportunity for churches to step up their charity game and feed the hungry. Never should have been the Government's job.