| commit | 1717c40c39135ec6f2cc8d617d49629b710d286c | [log] [tgz] |
|---|---|---|
| author | dschinazi <dschinazi@google.com> | Fri Aug 13 16:34:00 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 23 14:05:14 2021 -0700 |
| tree | ef2875c092304b7d6f000d7b600543eb1e6f106a | |
| parent | b16c8a22d7377ed41c7b5ca214122f8ba72ff86e [diff] |
Randomize the order of sent transport parameters As per RFC 9000, the order in which transport parameters are sent carries no semantics. To avoid ossification or fingerprinting, this CL randomizes the order they are sent in. Protected by FLAGS_quic_reloadable_flag_quic_randomize_transport_parameter_order. PiperOrigin-RevId: 390717555
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:
QUICHE is only supported on little-endian platforms.