We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
go version
$ go version go version go1.13.3 linux/amd64
Yes
go env
$ go env GOARCH="amd64" GOHOSTARCH="amd64" GOHOSTOS="linux" GOOS="linux"
I have created an HTTP2 client that connects to an HTTP2 server.
On the server side I do the following:
[]byte{0xAA, 0xBB}
flush()
[]byte{0xCC, 0xDD}
On the client side I read the incoming data.
Here is the testing code: https://play.golang.org/p/OtrJ7wW62Ud
On the client side I expect to do the first call to Read() to obtain []byte{0xAA, 0xBB} and on a second call to Read() obtain []byte{0xCC, 0xDD}
Read()
Instead on the first call to Read() I obtain []byte{0xAA, 0xBB, 0xCC, 0xDD}
[]byte{0xAA, 0xBB, 0xCC, 0xDD}
The text was updated successfully, but these errors were encountered:
Neither HTTP/2 nor io.Reader has semantic record boundaries. It's just a byte stream.
Closing, as I don't see any action required here on our side.
Sorry, something went wrong.
No branches or pull requests
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I have created an HTTP2 client that connects to an HTTP2 server.
On the server side I do the following:
[]byte{0xAA, 0xBB}
flush()
[]byte{0xCC, 0xDD}
flush()
On the client side I read the incoming data.
Here is the testing code:
https://play.golang.org/p/OtrJ7wW62Ud
What did you expect to see?
On the client side I expect to do the first call to
Read()
to obtain[]byte{0xAA, 0xBB}
and on a second call toRead()
obtain[]byte{0xCC, 0xDD}
What did you see instead?
Instead on the first call to
Read()
I obtain[]byte{0xAA, 0xBB, 0xCC, 0xDD}
The text was updated successfully, but these errors were encountered: