| commit | e8a887ba6e714527543e00fec419581cc40f42d8 | [log] [tgz] |
|---|---|---|
| author | elburrito <elburrito@google.com> | Mon Mar 11 13:06:48 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 11 13:07:57 2024 -0700 |
| tree | d777cb581a639be24aca24d5c8a2d44d1b0319db | |
| parent | 465d154154ff184acf343c5aaa0e011603cf2da5 [diff] |
BlindSignAuth: Refactoring to support future Android BlindSignMessageInterface impl. - Rename BlindSignHttpInterface to BlindSignMessageInterface - Change BSA::GetTokens oauth_token parameter to std::optional<std::string>, since Android BSA callers will not have an OAuth token to pass in - Change BlindSignMessageInterface::DoRequest authorization_header to std::optional<std::string> - Stop setting oauth_token field in AuthAndSignRequest (field is unused for IP Protection and will be deprecated) PiperOrigin-RevId: 614767846
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.