| commit | d2727921cf0de85009e7d774995dc7efa4009202 | [log] [tgz] |
|---|---|---|
| author | martinduke <martinduke@google.com> | Thu May 12 12:12:01 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu May 12 12:13:10 2022 -0700 |
| tree | c560ca42225eb632d72607fc9c113eb235b34582 | |
| parent | ba6200ced1190740736cd9f30a1010049c76312f [diff] |
Access buffered CHLO in the correct place when the server changes the connection ID. Modified HTTP e2e tests to usually check the case where the connection ID case is 16B. Bugs are filed for test failures, then the tests edited to bypass those cases. PiperOrigin-RevId: 448307373
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.