| commit | 190477e30f96f4fc2686517473a1763249981bce | [log] [tgz] |
|---|---|---|
| author | danzh <danzh@google.com> | Mon Oct 11 14:48:12 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 11 14:49:47 2021 -0700 |
| tree | 280c0fae521b3c43918923603193fe7136c3e746 | |
| parent | d9e16940859d20084e9de2b47450ca64d179d017 [diff] |
Support Http3 extended CONNECT. When QuicSpdySession::allow_extended_connect_ is true, ENABLE_CONNECT_PROTOCOL will be 1 in SETTINGS frame. The client sets allow_extended_connect_ to true once the received SETTINGS frame has ENABLE_CONNECT_PROTOCOL = 1. QuicSpdySession::allow_extended_connect_ is behind --gfe2_reloadable_flag_quic_verify_request_headers. Validate request pseudo headers, especially CONNECT with :protocol header when allow_extended_connect_ is true. Make webtransport support depends on allow_extended_connect_. And on server side, allow_extended_connect_ is always true if ShouldNegotiateWebTransport() returns true. Protected by quic_reloadable_flag_quic_verify_request_headers. PiperOrigin-RevId: 402397389
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.