commit | f16e5a92bb55c438f0c96def92e73ca7f67b3f09 | [log] [tgz] |
---|---|---|
author | dschinazi <dschinazi@google.com> | Fri Dec 06 15:40:18 2024 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Dec 06 15:41:14 2024 -0800 |
tree | 5df448405018e64c64f91474e1aade607119f43f | |
parent | 98664f0b3410e2010accb51ce42a8bffa9637189 [diff] |
Set a minimum number of chaos protection in new protector This simplifies testing whether chaos protection was performed since now we're guaranteed to get extra frames. This CL also adds a new e2e test for chaos protection v2, which test ensures that multi-packet chaos protection works as expected with kyber enabled. In particular, it ensures that retransmissions behave correctly. This change is only made in the new protector, which is behind a flag that is still enabled_blocked_by. Protected by FLAGS_quic_reloadable_flag_quic_enable_new_chaos_protector. PiperOrigin-RevId: 703637630
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.