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
{{ message }}
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.
When attempting an upgrade, content modifiers will be ignored and then an event is fired. However, when the HTTP/2 filters aren't installed, this event isn't handled. and thus the logic to handle the upgrade doesn't reset this flag. Because of these, a request body could be fully buffered, but the last flag on the HttpContent buffer is never set causing any further attempts to read in an attempt to get to EOF, to timeout.
The text was updated successfully, but these errors were encountered:
rlubke
changed the title
HTTP/2 Upgrade attempt with Grizzly 2.3.x with payload could end up timing out.
HTTP/2 Upgrade attempt without the HTTP/2 filters in use with a payload could end up timing out.
Sep 29, 2017
When attempting an upgrade, content modifiers will be ignored and then an event is fired. However, when the HTTP/2 filters aren't installed, this event isn't handled. and thus the logic to handle the upgrade doesn't reset this flag. Because of these, a request body could be fully buffered, but the last flag on the HttpContent buffer is never set causing any further attempts to read in an attempt to get to EOF, to timeout.
The text was updated successfully, but these errors were encountered: