| commit | 48e5979ddcc420ba5e3f47a469848e6381ddc05f | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Thu Jul 31 08:30:11 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 31 08:31:05 2025 -0700 |
| tree | d8f583681b4c86995109341dba4a164b5c3383bf | |
| parent | e693ba79bd17156b5ece9099b9fba4783757fccd [diff] |
Add `QuicheCodeCounter` to help size the impact of b/433557986 We are particularly interested in understanding the counts of the request parsing but we also add logging for response parsing to help us size their impact independently. If the count of `balsa_frame_framing_found_valid_term2_[request|response]` ends up being small enough, we can enforce RFC compliance unconditionally when reading the last chunk term. Protected by refactor and incrementing of streamz. PiperOrigin-RevId: 789347949
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.