- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
hey, at least it’s not a 200 with
{ "error": "Bad request" }Yeah, plus a 500 is the backend admitting it fucked up and not blaming the front end like a 4xx would be.
Quick, make a ticket to the network team and ask why the firewall is causing the internal server error.
I wish I could say I haven’t seen devs do this.
Oh even better. I manage Kong (an API manager) and 90% of my time these days is explaining illiterate devs that no, Kong is fine, it’s their shitty API crashing. Or better, their shitty HAproxy they don’t know how to configure. FML.
In some architectures, where many microservices are behind load balancers and other front end proxies, sometimes it is the NOC’s fault. Yes a 500 should really only be a backend error.
Fuck yes, Perry Bible Fellowship.
Best web comic of all time, hands down.
Could be worse. You could just have your socket disconnect because the back end process crashed.
Except when it’s a front-end script causing issues and blaming it kn the backend.
