Google GitGoogle Git
Sign in
quiche/quiche/90b03f4305f6513cd145ab9cab26e8d5620ca294
commit
90b03f4305f6513cd145ab9cab26e8d5620ca294
[log]
author
QUICHE team <quiche-dev@google.com>
Wed Jun 17 05:03:09 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Jun 17 05:03:38 2026 -0700
tree
beaa3dbf0b28a236138e97a1e20b8a3eec12a063
parent
980d52e0b98b7a81f9e4620903e6dd7642bc9c04 [diff]
Add generator script for Structured Header tests.

This CL adds `third_party/quiche/tools/generate_structured_headers_tests.py`, which programmatically fetches and translates JSON test cases from the HTTPWG structured-field-tests repository into C++ unit tests for QUICHE.

The script supports fetching from a specific commit hash and automatically discovers all relevant JSON test files in the repository.

`third_party/quiche/common/structured_headers_generated_test.cc` has been re-generated using this script at commit faed1f92942abd4fb5d61b1f9f0dc359f499f1d7 (the commit mentioned in the original file) to verify the script's correctness while maintaining a minimal diff.

It's unclear to me why a number of tests that existed at that commit were omitted from the generated test file originally.

PiperOrigin-RevId: 933655541
1 file changed
tree: beaa3dbf0b28a236138e97a1e20b8a3eec12a063
  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

Logging

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.