| commit | 89d8da3584ec003f42b5e8dc48cabbdf30c63072 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Thu Oct 30 16:43:18 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 30 16:44:22 2025 -0700 |
| tree | 0ac1ad8b62e6b90efaee7a69e8be4880b49fdda1 | |
| parent | 83bd4c083927c52a418ef4694780e36176779432 [diff] |
Add helper methods to check a string's RFC 9110, 5.6.2 compliance https://datatracker.ietf.org/doc/html/rfc9110#section-5.6.2 shows the grammar for a `token` and gives an _inclusive_ listing of characters. Balsa does not currently have a helper which exactly matches this listing of characters. The closest thing we have is the _exclusive_ list `kInvalidHeaderKeyCharList` which _almost_ matches this inclusive list with the exception of `:` for the set of US-ASCII characters. We add the helper here for use by future changes. Protected by adding helper method for future CL. PiperOrigin-RevId: 826236709
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.
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.
Usage: quic_packet_printer server|client <hex dump of packet>
Usage: crypto_message_printer_bin <hex of message>
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>
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