That was my first thought, I was struggling with stripping the gibberish, but I'll keep that in mind. I'm building both the server and client in this case so I don't mind handling it client-side, but when possible I'm hoping to provide an at least somewhat sanitized error to the client in the event that I pass on client development later. Thanks for that code snippet, I'll try that out on the client side and see which approach is more workable for now.