Google Git
Sign in
quiche/quiche.git/61a8de96f09228a1b2ecb7eb5bf50fb0809ab087
commit
61a8de96f09228a1b2ecb7eb5bf50fb0809ab087
[log]
author
reubent <reubent@google.com>
Wed Apr 15 08:37:54 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Apr 15 08:38:20 2026 -0700
tree
a3e702d8e9f1192cbf7551a8d2f3f8cd28cade22
parent
a7f9eeff891503e798e24e5dd88a90cda54e48ca [diff]
Reset streams which surpass MAX_HEADER_LIST_SIZE

A prior CL introduced this enforcement and set the result of streams which surpassed this limit as a HEADER_HTTP_MESSAGING error. With the current way oghttp2 is integrated into Envoy, HTTP messaging errors are treated as connection failures and to keep the behavior between nghttp2 and oghttp2 consistent, we reduce the severity to a stream reset. Also get rid of a duplicative test since we no longer allow the option to either tear down the connection or reset the stream.

Protected by unused oghttp2 option, enforce_max_header_list_bytes.

PiperOrigin-RevId: 900184337
3 files changed
tree: a3e702d8e9f1192cbf7551a8d2f3f8cd28cade22
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. .bazelversion
  6. BUILD.bazel
  7. CONTRIBUTING.md
  8. LICENSE
  9. MODULE.bazel
  10. MODULE.bazel.lock
  11. README.md
  12. WHITESPACE
README.md

QUICHE

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.

Build and run standalone QUICHE

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.

  • quic_packet_printer: from a provided packet, parses and prints out the contents that are accessible without decryption.

Usage: quic_packet_printer server|client <hex dump of packet>

  • crypto_message_printer: dumps the contents of a QUIC crypto handshake message in a human readable format.

Usage: crypto_message_printer_bin <hex of message>

  • quic_client: connects to a host using QUIC and HTTP/3, sends a request to the provided URL, and displays the response.

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>

  • masque_server: a MASQUE tunnel proxy that defaults to port 9661.

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