-
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
ShutdownOutput for non-persistent HTTP/1 connections #12212
Comments
@sbordet This issue was added in #9287 and it suppressed a real problem added with https://github.com/jetty/jetty.project/pull/9684/files#r1192999081 where we are now not always shutting down the output. Instead we now rely on the thrown exception |
I've reopened this issue, as I think there is a further problem with shutdownOutput. In previous versions of jetty, we did the shutdown as the last write completed. We are now doing it as the handling callback is completed, which may be very much later than when the response is sent. @sbordet thoughts? |
* Improve shutdown of non-persistent HTTP/1 connections + shutdown in SendCallback Signed-off-by: Simone Bordet <simone.bordet@gmail.com> --------- Signed-off-by: Simone Bordet <simone.bordet@gmail.com> Co-authored-by: Simone Bordet <simone.bordet@gmail.com>
Jetty version(s)
12
Enhancement Description
Currently a needless exception is thrown by the HttpConnection class after every connection is closed:
This can be seen if debug is turned on for the following test server
and then requests like the following are sent:
The text was updated successfully, but these errors were encountered: