Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
in my case, our infosec department wants all status to be 200 series and their reason is to mislead hackers that whatever the f* they'll do to the system, it will always be OK.
sounds like you need to hire new front-end devs...
C0D4705074yIf the crapheads can’t do their job, make their life miserable.
They’ll either work it out or never deliver anything.
Aedath1574yWell, Internal Server Error is usualy reserved for unhandled exceptions and should be returned by server/api and not your code. And as far as I know, it's okay to return a 200 with an error body if the frontend can handle it. It's like returning Not Found when your search query didn't find anything. It can be confusing. Then you start wondering if the Not Found was returned because you have a bad api route or did your search didn't find anything. At least that's the way I see it.