Add `max_header_bytes` to OgHttp2Session::Options() and send in initial SETTINGS.

This configurable option allows OgHttp2Session's HPACK decoder to adjust its
decoding buffer size and max allowed header block size in a similar strategy to
Http2Dispatcher [1]. This change is important to allow OgHttp2Session to decode
headers following Envoy's `max_headers_kb_` [2].

When locally added to Envoy's Http2Options [3], this change allows the
following codec_impl_tests to pass: LargeRequestHeadersAtLimitAccepted,
LargeRequestHeadersInvokeResetStream, LargeMethodRequestEncode,
LargeRequestHeadersOverDefaultCodecLibraryLimit (arguably no longer needed),
LargeRequestHeadersAtMaxConfigurable, LargeRequestHeadersAccepted.

[1] e.g., http://google3/gfe/gfe2/http2/;l=221-226;rcl=414330428
[2] http://google3/third_party/envoy/src/source/common/http/http2/codec_impl.h;l=549;rcl=414330428
[3] http://google3/third_party/envoy/src/source/common/http/http2/codec_impl.h;l=196;rcl=414009764

PiperOrigin-RevId: 415087562
3 files changed
tree: 8c128731e3c8b2d0d47484201061b5cadcf35207
  1. common/
  2. epoll_server/
  3. http2/
  4. quic/
  5. spdy/


QUICHE stands for QUIC, Http/2, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.

There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:

To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:

To contribute to QUICHE, follow instructions at

QUICHE is only supported on little-endian platforms.