net/http: HTTP/2 SETTINGS frame being read incorrectly #37059
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
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 outputted all HTTP/2 frames that are received by the net/http server corresponding to their type, and when looking at the SETTINGS frames the first settings ID always appears to be wrong.
For example, the first setting from Chrome is 0x1 or SETTINGS_HEADER_TABLE_SIZE, but the ID outputted by when looping through the settings in the frame is 239 when the expected value is 1.
Another example would be when I used Go's http.Client and the first setting is always 0x2 or SETTINGS_ENABLE_PUSH, but the outputted value 16384 when the expected value is 2.
What did you expect to see?
(Read above for explanation on what I'm talking about)
Expected first setting ID from latest Chrome: 1, SETTINGS_HEADER_TABLE_SIZE
Expected first setting ID from Go's http client: 2, SETTINGS_ENABLE_PUSH
What did you see instead?
(Read above for explanation on what I'm talking about)
"Received" first setting ID from latest Chrome: 239
"Received" first setting ID from Go's http client: 16384
The text was updated successfully, but these errors were encountered: