-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[UNDERTOW-2207][UNDERTOW-2212][UNDERTOW-2239][UNDERTOW-2252] 2.2.x backport bug fixes #1457
Conversation
Previously, setting Content-Length would auto-close the stream in such a way that a flush after the final write would throw an IOException due to internal self-closure.
…not checked by the undertow client Signed-off-by: Flavia Rainone <frainone@redhat.com>
… do not enforce the exception to be of type ClosedChannelException (see UNDERTOW-2249). Signed-off-by: Flavia Rainone <frainone@redhat.com>
…pt to wrap if engine.isInboundDone() Signed-off-by: Flavia Rainone <frainone@redhat.com>
…leak Signed-off-by: Flavia Rainone <frainone@redhat.com>
d5a8688
to
f0a0f24
Compare
Hi @fl4via |
@linkdonghh for 2.2.24.Final we will just close these Jiras and do a release right away. I'll get you an updated info on the next 2.2.25.Final release in a bit, hold on and I'll get back to you with the link. |
2d6dddc
to
f0a0f24
Compare
@linkdonghh Sorry for the delay in getting back to you, I was away during part of last week. |
@fl4via Hi, any news on this? is there a way we can help with 2.2.25.Final release? |
Jiras:
https://issues.redhat.com/browse/UNDERTOW-2207
https://issues.redhat.com/browse/UNDERTOW-2212
https://issues.redhat.com/browse/UNDERTOW-2239
https://issues.redhat.com/browse/UNDERTOW-2252