-
Notifications
You must be signed in to change notification settings - Fork 641
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
Connection prematurely closed DURING response #2944
Labels
type/bug
A general bug
Milestone
Comments
Aliaksie
added
status/need-triage
A new issue that still need to be evaluated as a whole
type/bug
A general bug
labels
Oct 27, 2023
violetagg
removed
the
status/need-triage
A new issue that still need to be evaluated as a whole
label
Oct 30, 2023
@Aliaksie I'm gonna work on this one. |
.retry(1) |
I also have the same problem |
@weiyouren how do you fix this error? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Possible similar to link or link
-> client send large multipart RQ
-> server receive
-> check size and throw 413
-> we catch it in our error handler and return 413 with json RS
-> server send completed
-> server on TERMINATED check if it consume full RQ
-> send new IOException("unconsumed input") and close connection
-> if the client has not yet completed processing, then it will receive an error and crash, otherwise it can complete the request smoothly (for example turn on DEBUG logs for jetty server).
Expected Behavior
the client will complete without error. I got 413 with json body.
Actual Behavior
the client does not complete consistently. I often get an error:
Steps to Reproduce
check the demo-repo
Possible Solution
add
.header( "Connection", "close" )
for file upload than here_generator.isPersistent()
will alwaysfalse
Your Environment
The text was updated successfully, but these errors were encountered: