Google Git
Sign in
quiche/quiche.git/8cc7cab04c839003b2aa9ced5c4fa8d88dc104f9
commit
8cc7cab04c839003b2aa9ced5c4fa8d88dc104f9
[log] [tgz]
author
martinduke <martinduke@google.com>
Wed Feb 04 09:09:51 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Wed Feb 04 09:10:44 2026 -0800
tree
7584d345b5065707374bc0607ab418eaf709da34
parent
dc02e7f61fb614c44ebe2f8a44672f2ecb25e321 [diff]
Make improvements to MoqtNamespaceStream.

Apologies for having another CL on this topic, but there are several fixes here:
- Setting the ObjectsAvailableCallback is no longer a separate operation in the NamespaceTask. This is an anti-pattern from FETCH that is suboptimal and causes problems when retrieving namespaces from the relay tree.

- IncomingSubscribeNamespaceCallback took std::optional<parameters> because it was also invoked on Unsubscribe. Now that is achieved by destroying the task, so Parameters are always present.

- There was a mistake in the test where task_ was assigned twice.

- There was no actual backpressure in the ObjectsAvailableCallback implementation.

- Got rid of std::move() when invoking multiuse callbacks.

PiperOrigin-RevId: 865435838
7 files changed
tree: 7584d345b5065707374bc0607ab418eaf709da34
  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