| commit | b5d556774fb971506e5912a357f0f8fb8ef08d12 | [log] [tgz] |
|---|---|---|
| author | rch <rch@google.com> | Thu Feb 01 14:48:45 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 01 14:50:13 2024 -0800 |
| tree | 6c160f26ae9c5c89f163e38866ba5ba1cf8973ce | |
| parent | 1ed2fb6c3ddce22a0baba689c16b76c53471013a [diff] |
Add a QUIC protocol flag to not require the the kSPAD connection option in order to use QUIC server preferred address support. quic_always_support_server_preferred_address defaults to false to match existing behavior but may be set to true. This will make it easier for QUICHE servers to support non-QUICHE clients using server preferred address. For context: https://github.com/envoyproxy/envoy/pull/32130 PiperOrigin-RevId: 603488744
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.