At a prior job, our ~~API~~ load balancers would swallow all errors and return an HTTP 200 response with no content. It was because we had one or two clients with shitty integrations that couldn't handle anything but 200. Of course, they brought in enough money that we couldn't ever force them to fix it on their end.

[–] herrvogel@lemmy.world 28 points 5 days ago

I once worked on a project where the main function would run the entire code in a try-catch block. The catch block did nothing. Just returned 200 OK. Didn't even log the error anywhere. Never seen anything so incredibly frustrating to work on.

[–] bleistift2@sopuli.xyz 5 points 5 days ago (2 children)

Why not POST /to/the/api?withCorrectErrorCodes?

[–] CrackedLinuxISO@lemmy.dbzer0.com 5 points 5 days ago

There was nothing RESTful or well planned about this API's interfaces, and the work to do something like that would have been nontrivial. Management never prioritized the work.

[–] tiredofsametab@fedia.io 2 points 4 days ago

Assuming there was some API key system in place, could just check on the key to see if it belongs to one of those clients. If yes, 200. Else, real APIs.

[–] Tum@lemmy.world 1 points 5 days ago

I think we might have worked at the same company. Did it begin with a K?