| commit | 49e65a4576c028e01227ce51ab3a7b76c36eb1bf | [log] [tgz] |
|---|---|---|
| author | birenroy <birenroy@google.com> | Thu Jan 11 12:19:11 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jan 11 12:20:47 2024 -0800 |
| tree | 181b9a9b155fe2b668e34b52152f354f11e3ee6e | |
| parent | 5f7c70d3291ecfbc9ffe07bea8f6cbe55568389f [diff] |
Fixes a code defect reported in https://github.com/envoyproxy/envoy/issues/31710. In a very specific situation, OgHttp2Session can enter an infinite loop. This requires the following conditions: * a stream has both response body data and trailers to write; * the stream becomes blocked by stream-level flow control while writing the body; and * the connection still has flow control quota available. In this circumstance, OgHttp2Session::HasReadyStream() returns true because trailers_ready_ is not empty, but WriteForStream() cannot make progress. The fix is to remove the stream ID from trailers_ready_ in GetNextReadyStream(). Protected by not protected, does not affect the GFE binary. PiperOrigin-RevId: 597622882
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.