-
Notifications
You must be signed in to change notification settings - Fork 2k
Issue #13670 - Returning ISE in all getParameter use cases outlined by Servlet 6.1 spec #14203
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
base: jetty-12.1.x
Are you sure you want to change the base?
Conversation
janbartel
left a comment
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.
Looks good, niggle about the javadoc as per comment.
| /** | ||
| * <p>Exception thrown to indicate a Bad HTTP Message has either been received | ||
| * or attempted to be generated. Typically these are handled with either 400 | ||
| * or attempted to be generated. Typically, these are handled with either 400 |
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.
Either doesn't make sense here unless another way of handling them other than a 400 response is listed.
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.
Also, is now the only reason to keep this class is ee < 11 ?
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.
Now bigger than Ben Hur!
Fixes #13670 as an alternate to #13678
Use the existing HttpException mechanism. Perhaps BadMessageException could be deprecated.
Prefer HttpException.IllegalStateException over BadMessageException, to not generate the wrong exception type in the first place.