-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
HTTP/2 UniformStreamByteDistributor stream window ignored #4545
Comments
@nmittler - FYI |
@Scottmitch good catch! ... do you want to throw together a PR with the updated test? |
@Scottmitch sgtm, thanks! |
pr pending ... |
Scottmitch
added a commit
to Scottmitch/netty
that referenced
this issue
Dec 23, 2015
Motivation: If the stream window is negative UniformStreamByteDistributor may write data. This is prohibited by the RFC https://tools.ietf.org/html/rfc7540#section-6.9.2. Modifications: - UniformStreamByteDistributor should use StreamState.isWriteAllowed() Result: UniformStreamByteDistributor is more complaint with HTTP/2 RFC. Fixes netty#4545
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
UniformStreamByteDistributor will write to a stream even if the stream's flow control window is negative. This is not allowed by the rfc.
https://tools.ietf.org/html/rfc7540#section-6.9.2
I guess the spec also means that you should not send new flow control frames until the flow-control window becomes non-negative? If the flow-control window is 0 and we have empty frames I don't think it should be a problem to send these.
While working on PR #4538 I developed the following test case to demonstrate the issue:
The text was updated successfully, but these errors were encountered: