| commit | 8fe40126cddce434394147f619ff5e30d328321d | [log] [tgz] |
|---|---|---|
| author | dschinazi <dschinazi@google.com> | Thu Nov 14 21:08:42 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 14 21:09:36 2024 -0800 |
| tree | 0796ea0e2bf40324a2c2704ecefcf4f1dc544eea | |
| parent | 390a10b25f7448d5f17f1bdef0662026dfc3113c [diff] |
Allow chaos protection with ACK frames This CL changes the new code path (only run when --gfe2_reloadable_flag_quic_enable_new_chaos_protector=true) to allow other frame types for ChaosProtection. In practice this just means that we might use chaos protection when there are both CRYPTO and ACK frames in the packet. Note that --gfe2_reloadable_flag_quic_enable_new_chaos_protector is currently marked with enabled_blocked_by so this change is protected by that flag. Also note that this functionality is exercised by the tests that were modified in cl/686534601. This CL also removes an error log that was accidentally introduced in cl/696443185. Protected by FLAGS_quic_reloadable_flag_quic_enable_new_chaos_protector. PiperOrigin-RevId: 696752156
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.