| commit | 1a82c3c7ef44670191c5dee9511f4ab9f02cce64 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Mon Jun 23 17:40:47 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 23 17:41:38 2025 -0700 |
| tree | 73f66c50b2c7f6af41e362d4a1f0a69a2a72d105 | |
| parent | 0b5e445de64c22251a35a8b1c805e0d5723fca94 [diff] |
Fix Known-Length BHTTP frame decoding The current logic assumes the framing indicator is only one byte, but [RFC 9292](https://www.rfc-editor.org/rfc/rfc9292.html) states that the request and response framing indicators use the variable-length integer encoding from [RFC 9000](https://www.rfc-editor.org/rfc/rfc9000#section-16) and that values do not need to be encoded on the minimum number of bytes necessary. This means the logic has to also handle 2, 4, and 8-byte long values. Protected by Tests, this change still handles the 1-byte framing indicator. PiperOrigin-RevId: 774991715
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.