|author||QUICHE team <firstname.lastname@example.org>||Wed Jan 19 14:25:01 2022 -0800|
|committer||Copybara-Service <email@example.com>||Wed Jan 19 14:25:59 2022 -0800|
Fix content-length validation for trailers. This CL fixes a bug in content-length validation when trailers end the stream: 1. End of headers, stores content-length for validation 2. End of data, does not end stream and does not match content-length 3. End of trailers, ends stream and stores content-length for validation (!) The re-storing of content-length at the end of trailers erases the previous validation at the end of data. This CL fixes Step 3 to avoid storing content-length for trailers. MultiplexedIntegrationTest.InconsistentContentLength: http://sponge2/e572060c-8ff8-45a8-b3b3-25994345b2bb (demonstrates RST_STREAM) PiperOrigin-RevId: 422904538
QUICHE stands for QUIC, Http/2, 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.