-
Notifications
You must be signed in to change notification settings - Fork 18k
x/net/http2: missing SETTINGS_HEADER_TABLE_SIZE support #29356
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
Comments
Change https://golang.org/cl/155877 mentions this issue: |
@katiehockman: all other issues related to |
Just a mistake. Thanks for letting me know. Updated it. |
Change https://go.dev/cl/435899 mentions this issue: |
This patch looked close to landing, but discussion stalled out. I've rebased the patch from CL 155877, addressed the last piece of feedback I saw from Brad (splitting the MaxHeaderTableSize setting into two settings), added an additional test and published as a new CL. @neild or @bradfitz if you have time, I'd very much appreciate a review. |
Add support for handling of SETTINGS_HEADER_TABLESIZE in SETTINGS frames. Add http2.Transport.MaxDecoderHeaderTableSize to set the advertised table size for new client connections. Add http2.Transport.MaxEncoderHeaderTableSize to cap the accepted size for new client connections. Add http2.Server.MaxDecoderHeaderTableSize and MaxEncoderHeaderTableSize to do the same on the server. Fixes golang/go#29356 Fixes golang/go#56054 Change-Id: I16ae0f84b8527dc1e09dfce081e9f408fd514513 Reviewed-on: https://go-review.googlesource.com/c/net/+/435899 Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Joedian Reid <joedian@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Damien Neil <dneil@google.com>
There are TODO comments in the code about
SETTINGS_HEADER_TABLE_SIZE
support. Proper would:SETTINGS_HEADER_TABLE_SIZE
capped by the max table size definedI have a working implementation. I need to write tests and I will submit it.
Cc @bradfitz
The text was updated successfully, but these errors were encountered: