New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error code for invalid message format #342

Closed
jimsteel opened this Issue Apr 20, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@jimsteel

jimsteel commented Apr 20, 2016

It would be good if the server could throw 400-class errors (probably 400) rather than 500s in the case of invalid JSON/XML (e.g. propagated from a DataFormatException coming from a JsonParserException)

jamesagnew added a commit that referenced this issue Apr 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment