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
Tell why a request is bad for a 400 Bad Request response #1575
Conversation
Motivation: It is sometimes hard for a client to know why a request is bad. Modifications: - Added short error messages to 400 Bad Request responses - Used `ProtocolViolationException` instead of `IllegalArgumentException` for bad requests. - Removed unnecessary validation of HTTP method in `HttpServerHandler`. Result: - User friendliness.
/cc @jwills |
Codecov Report
@@ Coverage Diff @@
## master #1575 +/- ##
============================================
+ Coverage 72.77% 72.77% +<.01%
- Complexity 7495 7499 +4
============================================
Files 695 695
Lines 30171 30188 +17
Branches 3683 3687 +4
============================================
+ Hits 21956 21970 +14
- Misses 6310 6317 +7
+ Partials 1905 1901 -4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Thanks for reviewing. |
Motivation: It is sometimes hard for a client to know why a request is bad. Modifications: - Added short error messages to 400 Bad Request responses - Used `ProtocolViolationException` instead of `IllegalArgumentException` for bad requests. - Removed unnecessary validation of HTTP method in `HttpServerHandler`. Result: - User friendliness.
Motivation:
It is sometimes hard for a client to know why a request is bad.
Modifications:
ProtocolViolationException
instead ofIllegalArgumentException
for bad requests.HttpServerHandler
.HttpServerHandler
.Result: