| commit | 16114c23f0044cca27156e046962028e46e26afd | [log] [tgz] |
|---|---|---|
| author | haoyuewang <haoyuewang@google.com> | Thu Nov 10 05:29:22 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 10 05:30:54 2022 -0800 |
| tree | 1cccbbfac295720e7a4d3c2b023d672de58c4438 | |
| parent | 9bd00ee884b7ac4d7941647fa4d8887f41a0fc1e [diff] |
Use next_connection_id_sequence_number to validate retired CID number as retiring an active CID would not guarantee that a new CID is issued due to CID collision in dispatcher. Default enabled as a bug fix. Protected by FLAGS_quic_reloadable_flag_quic_check_retire_cid_with_next_cid_sequence_number. PiperOrigin-RevId: 487508836
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.