-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
None
Because those classes do not check for the remaining content length when writing and flush, we could have a mimatch caused by a bug in the servlet code, in case the servlet sets a content length that is not equal to the amount of bytes it is writing.
As a result, Undertow sends an invalid HTTP response, one where the content length header does not match the actual length of the response date.
This can cause issues with clients, and it causes issues with Undertow itself. When tests are run in proxy mode + HTTP2, we can see the proxy closes the stream when receiving the faulty header.
- blocks
-
UNDERTOW-2243 Eager flush/close on content length response prevents POST from finishing
- Closed
- is incorporated by
-
UNDERTOW-2507 Get 2.0.41.SP branch in good shape
- Pull Request Sent
-
WFCORE-6388 Upgrade Undertow to 2.3.7.Final
- Closed