| commit | 2a464c5105053295611521d82a31bb123daf2281 | [log] [tgz] |
|---|---|---|
| author | danzh <danzh@google.com> | Fri Apr 05 12:16:31 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 05 12:18:05 2024 -0700 |
| tree | 79ae61982b6296f7b3a746a85a2d76b8a20a8653 | |
| parent | cb9fb6cc8bf665065d3c1e13834666c3180e56e9 [diff] |
Fix flaky quic e2e test EndToEndTest.ClientPortMigrationOnPathDegrading. The test was flaky because the test server starts to drop packets before sending a NEW_CONNECTION_ID frame back to the client after 1st port migration. So the 2nd path degrading couldn't kick off another probing. PiperOrigin-RevId: 622248973
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.