| commit | 37c2bbe3ad4ae22543b69f4beaf5b7d9bf513dcb | [log] [tgz] |
|---|---|---|
| author | rch <rch@google.com> | Thu Feb 29 11:38:12 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 29 11:40:08 2024 -0800 |
| tree | 826cac220753cbcf2b9725831345b50fe55f4d07 | |
| parent | c6a366bc5ee56f32d26857a17e233568cdd9ae49 [diff] |
Add a new MetadataVisitor class to QuicSpdyStream. If registered, an instance of this new class will receive decoded HTTP/3 METADATA frames. If not, registered, HTTP/3 METADATA frames will be delivered as unknown HTTP/3 frames, which is current behavior. This is motivated by implements HTTP/3 METADATA handling in Envoy. Without this new visitor, we need to hook into the EnvoyQuicSession's OnUnknownFrame methods. But this is really annoying because we receive frames on the Stream, bounce them (at the QUICHE layer) over the the Session which parses them into Headers and then need to bounce them back over to the Stream. This is awkward. By using this new Visitor, the Stream itself can handle METADATA. Protected by FLAGS_quic_reloadable_flag_quic_enable_http3_metadata_decoding. PiperOrigin-RevId: 611542297
QUICHE stands for QUIC, Http, 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.