| commit | ae1fda7e0aea56c1ae219772a6e0843eb84b0995 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Fri Aug 01 08:00:23 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Aug 01 08:02:02 2025 -0700 |
| tree | 64682098bd8ee9872963503e577fbab83fefbc2c | |
| parent | 48e5979ddcc420ba5e3f47a469848e6381ddc05f [diff] |
Add new validation policy rejecting chunked requests framed with anything other than CRLFCRLF According to the [RFC](https://datatracker.ietf.org/doc/html/rfc9112#name-chunked-transfer-coding), the ABNF for chunked coding states that both `last-chunk` _and_ `chunked_body` must end with `CR_LF`. This implies that `kValidTerm2` should not allowed in this case. Protected by code is unused by any caller. PiperOrigin-RevId: 789764991
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.