Google GitGoogle Git
Sign in
quiche/quiche/4cbbadf0d645e9fafc71517dfef51481d4f796f0
commit
4cbbadf0d645e9fafc71517dfef51481d4f796f0
[log]
author
QUICHE team <quiche-dev@google.com>
Wed Sep 09 07:58:40 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Sep 09 08:00:09 2026 -0700
tree
e1b98c11ad731178d2ada55391f772e07f1142fe
parent
470da96b01bd69a175feb3f786c3b34bb7eaa7ad [diff]
quic: Rename kMaxValue histogram sentinels in QUIC enums

QUIC_CLIENT_HISTOGRAM_ENUM expects an exclusive enum count for
its enum_size parameter. PathValidationReason and
MultiPortStatusOnMigration defined an extra enumerator named
kMaxValue without an explicit value, making it act as an exclusive
count rather than an inclusive maximum value.

In Chromium, 3-argument UMA_HISTOGRAM_ENUMERATION() is changing to
disallow logging enums that define kMaxValue to prevent conflating a
count with a max value. Rename these boundary sentinels to kNumReasons
and kNumStatuses to reflect their semantics and prevent compile
errors when consumed by Chromium histogram macros.

PiperOrigin-RevId: 978548455
3 files changed
tree: e1b98c11ad731178d2ada55391f772e07f1142fe
  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.