Gracefully handle server errors that would result in a 500 and stacktrace
Closed this issue · 0 comments
ccjoel commented
Currently, in the event mysql is down, or any exception is thrown somewhere in code, the server responds to the client with an ugly text with the direct error message from the source.
We should add a handler at the server and return a 500, and maybe a json or some better message (or none?) instead of this raw message.