|author||dschinazi <email@example.com>||Thu Feb 10 09:12:48 2022 -0800|
|committer||Copybara-Service <firstname.lastname@example.org>||Thu Feb 10 09:13:27 2022 -0800|
Deprecate quic_ignore_key_update_not_yet_supported Context: before this implementation supported IETF QUIC key updates, we introduced a custom "key_update_not_yet_supported" transport parameter that was sent to indicate this version of the code did not support key updates. When we implemented key updates, we stopped sending the transport parameter, but would disable them if we received the transport parameter. This CL deprecates gfe2_reloadable_flag_quic_ignore_key_update_not_yet_supported which means that we now no longer act on receiving the transport parameter at all. Now that this transport parameter is no longer sent or parsed, it can be fully removed, along with all the machinery to negotiate key updates. Note that CL was originally reviewed at cl/425663257 and was rolled back via cl/426198777. We are now rolling this forward since we have fixed the Chrome merge issues via https://crrev.com/c/3451177. This CL does not have any changes from cl/425663257. PiperOrigin-RevId: 427765515
QUICHE stands for QUIC, Http/2, 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.