Google Git
Sign in
quiche/quiche.git/7c6eb2cb40b2157a4df9d54bfb409c57ffc1ce50
commit
7c6eb2cb40b2157a4df9d54bfb409c57ffc1ce50
[log]
author
QUICHE team <quiche-dev@google.com>
Wed Aug 12 09:34:50 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Aug 12 09:35:20 2026 -0700
tree
949dbf7ef64b9b8fe1a6d6eb5e870bb628c8677e
parent
309537f48651f481ed78b44380c42da5c0fb01bc [diff]
Guard SSL_set_reject_unusable_ech_config with BORINGSSL_API_VERSION >= 43.

`SSL_set_reject_unusable_ech_config` was introduced in BoringSSL while
`BORINGSSL_API_VERSION` was 42. OSS QUICHE CI builds against an older
pinned version of BoringSSL that is also on `BORINGSSL_API_VERSION == 42`,
which caused the build to break.

Guarding the usage with `#if BORINGSSL_API_VERSION >= 43` ensures OSS QUICHE
builds succeed until BoringSSL bumps `BORINGSSL_API_VERSION` to 43 and rolls.

Protected by FLAGS_quic_reloadable_flag_quic_reject_unusable_ech_config.

PiperOrigin-RevId: 963494594
2 files changed
tree: 949dbf7ef64b9b8fe1a6d6eb5e870bb628c8677e
  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.