commit | f7a27a9becfb51e861d564136d5c0f1504dd1768 | [log] [tgz] |
---|---|---|
author | dschinazi <dschinazi@google.com> | Tue Dec 10 15:02:47 2024 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Dec 10 15:03:59 2024 -0800 |
tree | 9bf9cd9db8bfbf772fa7c54463e07617ae8a21ff | |
parent | f517b654418cb4bd4145a230c0d99c0721d485ee [diff] |
Unblock quic_enable_chaos_protection_v2 flag Now that Chaos Protection v2 is feature complete and has good coverage in both unit tests and end-to-end tests, we're ready to start deploying it. This flag was originally called --gfe2_reloadable_flag_quic_enable_new_chaos_protector but multiple CLs landed behind it so we need to rename it before unblocking. We're renaming it to --gfe2_reloadable_flag_quic_enable_chaos_protection_v2. This CL unblocks --gfe2_reloadable_flag_quic_enable_chaos_protection_v2 for deployment on servers, and enables it in Chrome. PiperOrigin-RevId: 704858299
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.