-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
WritePendingException over HTTP/2 tunnel #10145
Comments
This is ultimately caused by the The semantic of In particular, |
Method HTTP2StreamEndPoint.flush() has a "no pending operation" semantic, but the previous implementation was calling stream.data(), which may become a pending operation if the stream is congested. Changed the implementation of flush() to return false in the IDLE and PENDING cases. Now every flush() is converted to a write(), which has the same semantic as stream.data(). Signed-off-by: Simone Bordet <[email protected]>
Method HTTP2StreamEndPoint.flush() has a "no pending operation" semantic, but the previous implementation was calling stream.data(), which may become a pending operation if the stream is congested. Changed the implementation of flush() to return false in the IDLE and PENDING cases. Now every flush() is converted to a write(), which has the same semantic as stream.data(). Signed-off-by: Simone Bordet <[email protected]>
Jetty version(s)
10+
Description
HttpClient
communicating to ahttps
server through a forward proxy via HTTP/2 tunnel.The text was updated successfully, but these errors were encountered: