| commit | 20220539a895bc66577781849abcca8d6e21e0dc | [log] [tgz] |
|---|---|---|
| author | wub <wub@google.com> | Mon Nov 01 12:15:32 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Nov 01 12:18:02 2021 -0700 |
| tree | 19acdb323f73fb3893c955a4b49c38d8da10ff2f | |
| parent | e6c3f38c3dc4e5b2510faaf417ef7199a073164e [diff] |
Pass ParsedClientHello to QuicDispatcher::CreateQuicSession. This makes it easier to pass CHLO information into CreateQuicSession, which is responsible for creating a QUIC session. The information I'd like to add into ParsedClientHello, in a follow up CL, are - Whether TLS resumption is attempted - Whether Early Data is attempted - The address token from the last packet of a CHLO, which will contain CachedNetworkParameters after cl/405481550. PiperOrigin-RevId: 406887508
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.