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 }}
Repository navigation
http2: a handler that answers past the client's window without reading its body hangs a client that uploads everything before it reads #588
Some clients finish their upload before they read the response. A handler that answers such a client with more than its stream window, without reading the request body, hangs until the client times out. .NET's HttpClient does this when it uploads a StreamContent, which is not duplex. Seen with a 256 KiB streamed 413 over h2c, both before and after #582.
Cause. The unread body holds the 65,535-byte connection window, so the upload stalls. The client credits the response only after its upload ends, so the response never reaches END_STREAM. #582's reset waits for END_STREAM, so it never goes out either.
Fix. Credit and drop the body of a request whose handler has returned, before its response ends, so that the upload can finish. A connection window larger than 65,535 (#569) would only move the threshold. #582's E2E test keeps its h2 answer inside the window for this reason.
Closing as not planned. A client that reads its response only after it has sent its whole request (.NET HttpClient with a non-duplex content, for one) and gets an early answer larger than its stream window waits until its own timeout, as it would with nginx or Go: the server won't drain its upload to rescue it. A client that reads while it uploads, which hung because nothing told it to stop, is handled by #633, which sends RST_STREAM(NO_ERROR) after such an answer; early answers that fit the client's window already got one.
Activity
http2: an answer that waited on the client's credit is followed by RS…
MDA2AV commentedon Nov 15, 2026
Closing as not planned. A client that reads its response only after it has sent its whole request (.NET HttpClient with a non-duplex content, for one) and gets an early answer larger than its stream window waits until its own timeout, as it would with nginx or Go: the server won't drain its upload to rescue it. A client that reads while it uploads, which hung because nothing told it to stop, is handled by #633, which sends RST_STREAM(NO_ERROR) after such an answer; early answers that fit the client's window already got one.
http2: a stream's window is credited a quarter of it at a time instea…