Add an `oghttp2` option to cap outbound DATA frame payload size. `oghttp2` sizes outbound DATA frames up to the peer's `SETTINGS_MAX_FRAME_SIZE`, while `nghttp2` always caps them at 16 KB. Envoy's `WINDOW_UPDATE` flood protection budgets inbound `WINDOW_UPDATE` frames per outbound DATA frame, so a client that advertises a large `MAX_FRAME_SIZE` and acknowledges data in small chunks gets far fewer DATA frames under `oghttp2` and trips the flood limit. Add `max_outbound_data_frame_payload` to `OgHttp2Session::Options`. When set, outbound DATA frames are capped at the smaller of this value and the peer's `MAX_FRAME_SIZE`. The option is unset by default (zero is treated as unset), so existing behavior is unchanged. Envoy can set it to 16 KB behind a runtime flag to match `nghttp2` framing. Context: https://docs.google.com/document/d/19f6B6MpH0VX-pEq2KPTutGqPd7w1CTrGw-iD_5x6Yn4/edit?tab=t.0#heading=h.rjkpiys4lyzb PiperOrigin-RevId: 992426536
QUICHE stands for QUIC, Http, 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 CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.
QUICHE has binaries that can run on Linux platforms.
Follow the instructions to install Bazel.
sudo apt install libicu-dev clang lld cd <directory that will be the root of your quiche implmentation> git clone https://github.com/google/quiche.git cd quiche CC=clang bazel build -c opt //... ./bazel-bin/quiche/<target_name> <arguments>
There are several targets that can be built and then run. Full usage instructions are available using the --helpfull flag on any binary.
Usage: quic_packet_printer server|client <hex dump of packet>
Usage: crypto_message_printer_bin <hex of message>
Usage: quic_client <URL>
quic_server: listens forever on --port (default 6121) until halted via ctrl-c.
masque_client: tunnels to a URL via an identified proxy (See RFC 9298).
Usage: masque_client [options] <proxy-url> <urls>
Usage: masque_server
web_transport_test_server: a server that clients can connect to via WebTransport.
moqt_relay: a relay for the Media Over QUIC transport for publishers and subscribers can connect to.
Usage: moqt_relay
Most log messages in QUICHE use the QUICHE_DLOG macro. In standalone quiche, these all either go to stderr, or are suppressed, based on the --stderrthreshold flag.
To send INFO level log messages to a file, you would therefore invoke
<binary> <args> > <logfile> 2>&1
Use the --helpfull flag for more.