| commit | d6724b55015ae5735699b0ab457557f9daf32622 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Tue Apr 11 08:20:10 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 11 08:20:58 2023 -0700 |
| tree | e7efddc6185b0a905b08e342de7c1c9c12104f7b | |
| parent | 6c85daed0ab9ba40844320e5bf36456149390d31 [diff] |
Update fingerprint function to prevent intentional collisions If the backend and clients don't agree on the fingerprint algo, verification will fail. We'll need to patch this into beryllium at the end of the workday friday so minimum testers are affected. No production traffic uses public metadata, so this isn't a reliability concern warranting a careful migration strategy. PiperOrigin-RevId: 523406924
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.