| commit | be8fe12ae55d7ce4a5db2325abf0d3c832f699ed | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Fri Sep 02 08:10:18 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Sep 02 08:12:14 2022 -0700 |
| tree | 3869fa075824d851551e5daa030d52268ecb0928 | |
| parent | 5293996358eeeb99e96fd841714f611dc823509c [diff] |
Convert quic_bounded_crypto_send_buffer to a QUIC_PROTOCOL_FLAG Because we don't know what size customer certificates could be in the future, we don't anticipate enforcing this flag, and do not plan to verify it. Instead, convert to a QUIC protocol flag so that we have a mechanism to enforce the size limit if necessary in the future. Protected by quic_bounded_crypto_send_buffer. PiperOrigin-RevId: 471804475
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.