-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Improvements and cleanups to ErrorHandler. #11556
Conversation
Defaulted showStacks to false, to reduce false positives reported by penetration testing tools. Deprecated ErrorHandler.badMessageError(), as it was not invoked anymore. Implemented HttpStreamOverHTTP[2|3].onBadMessage() that was left as TODO. Simplified the same code for HTTP/1. Moved invocation of ComplianceViolation.Listener.onRequestEnd() to HandlerInvoker.completeStream(). Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
*/ | ||
@Deprecated(since = "12.0.8", forRemoval = true) | ||
public ByteBuffer badMessageError(int status, String reason, HttpFields.Mutable fields) |
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.
Is this really not called anymore by things like the HttpParser?
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.
No it is not.
In Jetty 11 it was called by HttpChannel
, but in Jetty 12 we handle failures differently by always calling HttpChannel.onFailure()
.
Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
@sbordet the CI failures are due to the new way we create a request in onFailure |
Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
@gregw yes I'm on it. I decided to restore the creation of the error request in HTTP/1.1 because it has more information. |
Defaulted showStacks to false, to reduce false positives reported by penetration testing tools.
Deprecated ErrorHandler.badMessageError(), as it was not invoked anymore.
Implemented HttpStreamOverHTTP[2|3].onBadMessage() that was left as TODO.
Simplified the same code for HTTP/1.
Moved invocation of ComplianceViolation.Listener.onRequestEnd() to HandlerInvoker.completeStream().