-
Notifications
You must be signed in to change notification settings - Fork 3.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
okhttp: okhttp client and server transport should use padded length for flow control #10422
Conversation
139dabe
to
3f54bfd
Compare
788a4b5
to
804d9a2
Compare
540265c
to
6933356
Compare
6933356
to
e4d26b5
Compare
e4d26b5
to
5746ac3
Compare
return createMessageFrame(stringMessage, 0); | ||
} | ||
|
||
private static Buffer createMessageFrame(String stringMessage, int paddingLength) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see the point of this new method, and it is a bit misleading. This seems to only work because nothing consumes the padding. When outside of the test, the buffer would have paddingLength-1 extra data, because 1 byte was consumed to communicate the padding length.
It seems this could just be removed and use the old non-padding-enabled creation.
fix #10018