| commit | 426c1ec2069bcae60261f8ac0509ac618c020e98 | [log] [tgz] |
|---|---|---|
| author | rch <rch@google.com> | Mon Jul 29 11:36:50 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 29 11:37:50 2024 -0700 |
| tree | 2384cff7bdff83bd48120f7d16c6b650bb36d087 | |
| parent | f4ed5e0c74485fb302367b833b8974373fed9e4c [diff] |
Add QUICHE support for the HTTP/3 ORIGIN frame. The ORIGIN HTTP/3 frame allows a server to indicate what origin or origins RFC6454] the server would like the client to consider as one or more members of the Origin Set (Section 2.3 of [ORIGIN]) for the connection within which it occurs https://www.rfc-editor.org/rfc/rfc9412.html Protected by FLAGS_gfe2_reloadable_flag_enable_h3_origin_frame. PiperOrigin-RevId: 657272516
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.