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.

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

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

[–] CrackedLinuxISO@lemmy.dbzer0.com 5 points 4 months 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.

load more comments (1 replies)

load more comments (3 replies)