| commit | 6c726cca04b68c5593fbded31fadb001771844ef | [log] [tgz] |
|---|---|---|
| author | danzh <danzh@google.com> | Wed Jul 09 08:28:21 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 09 08:29:12 2025 -0700 |
| tree | 54bc5c9c6d527210282313952afc1503275dc1ac | |
| parent | 5de6f0190c90eb060611399315d188f7b4cbdc2e [diff] |
Patch a fix from https://github.com/villainb-dg for the issue of leaking connection flow control window when a HTTP2 stream receives a DATA frame after being closed (reset, etc). When a stream receives a DATA frame while it is already closed, the data is counted against the connection flow control window, but is never marked as consumed. Fix: Mark the data as consumed when the received DATA frame is on a reset or invalid stream. Reported QUICHE issue https://github.com/google/quiche/issues/91 Reported Envoy issue https://github.com/envoyproxy/envoy/issues/40085 Proposed external fix: https://github.com/google/quiche/pull/92 PiperOrigin-RevId: 781064590
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.