| commit | 7c58a6ac043402c9148b02df4adef39bfa1226ce | [log] [tgz] |
|---|---|---|
| author | haoyuewang <haoyuewang@google.com> | Mon Aug 09 17:18:48 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 09 17:21:11 2021 -0700 |
| tree | 28fd21fb0fb8064a1ed403ed0a9c240a2a399b22 | |
| parent | 2f54a5505b9cbc343f365cbad491d09bbc268734 [diff] |
Consult self_issued_connection_id_manager instead of default_path_ for connection ID to look up session in session map. As a bug fix, gfe2_reloadable_flag_quic_use_active_cid_for_session_lookup is default enabled. Protected by FLAGS_quic_reloadable_flag_quic_use_active_cid_for_session_lookup. PiperOrigin-RevId: 389761333
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.