-> 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:
reactor.netty.http.client.PrematureCloseException: Connection prematurely closed DURING response
reactor.core.Exceptions$ReactiveException: reactor.netty.http.client.PrematureCloseException: Connection prematurely closed DURING response
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