> "intelligent" things in front of your code (load balancers, WAFs, browsers) start doing unpredictable things I've never had that happen, but instead have had

> "intelligent" things in front of your code (load balancers, WAFs, browsers) start doing unpredictable things I've never had that happen, but instead have had "intelligent" caching mess up my requests that returned 200 multiple times. Granted, most of the times it was a bad header that did not specify no-cache, but as far as I know, error codes are never cached. With 200 and caching, error body would continue to be returned for the cache's lifetime. > It also makes JavaScript fetch calls easier as your catch block will most likely be a hard down scenario. This I agree with, Javascript syntax just sucks for error handling.