| commit | bfc16b2a2a6a46c2823b48c12c4ec542f63d436d | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Wed Sep 10 13:55:31 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 10 13:56:33 2025 -0700 |
| tree | 7214ed89264a2ebca3521e0cceaad30ef758c753 | |
| parent | 9d1b1767fd3cd8108266c3bbb211918a805faa6c [diff] |
Switch QUIC client use new ALPS codepoint by default. GFE has been enabled to support both codepoint more than a year, we should set default to use the new codepoint for QUIC on the client side if there are no explicitly setting. Chrome side already turned on default to as part of [this change](https://chromiumdash.appspot.com/commit/220d59101b2f05932d29a5c1efb1091019096e4e). Protected by FLAGS_quic_reloadable_flag_quic_client_default_enable_new_alps_codepoint. PiperOrigin-RevId: 805503147
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.