> At a previous company, we returned a 200 for anything that was not a true HTTP error on our side I work at a company that does this and it is beyond annoying

> At a previous company, we returned a 200 for anything that was not a true HTTP error on our side I work at a company that does this and it is beyond annoying. We've had multiple discussions between the dev team and we chalk it up the difference between application developers, who want the error codes to reflect the state of the application, and network engineers, who want the error codes to reflect the state of the network. Both sides have merit, but as an app developer I really hate the networking engineer approach to this.