You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the fix for issue #126 here: #128, a bug was introduced where in the response for the first HTTP keep-alive request does not write the "LastHttpContent" and hence netty's HTTP decoder did not consider the response as complete.
This leads to a state where for subsequent responses, netty's HTTP decoder will ignore the HTTP headers as it thinks that the first response is not yet over.
As part of the fix for issue #126 here: #128, a bug was introduced where in the response for the first HTTP keep-alive request does not write the "LastHttpContent" and hence netty's HTTP decoder did not consider the response as complete.
This leads to a state where for subsequent responses, netty's HTTP decoder will ignore the HTTP headers as it thinks that the first response is not yet over.
This can be reproduced by this sample server:
and using Apache Bench command:
The following server log:
shows that for the second request, the server does not send the headers, but just sends the content "Hello World"
Thanks @brendangregg for debugging this!
The text was updated successfully, but these errors were encountered: