| commit | b45e7741802e3b1fbe5635ea6798df0ce0991a16 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Wed Jan 03 12:09:59 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 03 12:10:54 2024 -0800 |
| tree | 06f1a1ae3283475cb028959b20ff5d3af8aa1ecc | |
| parent | 87cb8c8ba9c05dbeb623177d5bba0ce43d38112d [diff] |
Inline expectations into EXPECT_QUIC_BUGs This prevents reading uninitialized results if EXPECT_QUIC_BUGs ever run as death tests. Chromium is in the process of removing the ability to cancel FATAL LogMessages (incl. the underlying LOG(DFATAL)s that EXPECT_QUIC_BUGs are detecting). With this change DefaultClientProofSource passes if EXPECT_QUIC_BUG is defined as EXPECT_DCHECK_DEATH in Chromium. PiperOrigin-RevId: 595468073
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.