| commit | 92390be5374605f113839dc6afecc484136fdf40 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Thu Jan 26 07:09:42 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jan 26 07:10:36 2023 -0800 |
| tree | 57455ad6ea8fce47a5b8c04725def3805a5bd3be | |
| parent | d4cfa3ee72ca627400653ab036f1e357ccacbcb5 [diff] |
Handle unsupported 100-continue as a Bad Request. With this CL, the client is able to get a clear message about their request failing due to unsupported 100-continue with the `GFE_RESPONSE_CODE_DETAILS_TRACE` header. They are also able to get `RC_BAD_REQUEST` with the `grpc-message` header. PiperOrigin-RevId: 504833222
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.