Google Git
Sign in
quiche / quiche / eec4080d1549e9e0423fcddf10172b7707d52ab9
commiteec4080d1549e9e0423fcddf10172b7707d52ab9[log] [tgz]
authorrch <rch@google.com>Tue Nov 25 18:16:17 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Tue Nov 25 18:17:07 2025 -0800
tree8513c2fd45807f6d9237ddb93f5566e5eb04e8aa
parent5d51e078453caf66cdc7f3b6abcf3c5b1926720a [diff]
Make it a `QUIC_BUG` to access the `QuicSession`'s `QuicConfig` after
the handshake completes, in preparation for dropping the config
completely to safe memory.

This CL moves the `QuicConfig` object into a new `SavedConfig` class
which the session stores instead. This new class provides accessors
to the underlying config which trigger the `QUIC_BUG` once the config
has been "deleted". (The actual deletion will happen in a follow up CL).

It also provide a new accessor for access to the config after deletion,
which callers will need to use to avoid the `QUIC_BUG`. In a follow-up
(flag-protected) CL, the `SavedConfig` will cache values from the
`QuicConfig` when it is deleted, and return those instead.

Project import generated by Copybara.

PiperOrigin-RevId: 836879510
5 files changed
tree: 8513c2fd45807f6d9237ddb93f5566e5eb04e8aa
  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