| commit | b4dfecd23c609556109a18a7521ef809bdc474e8 | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Wed Jan 26 10:17:04 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 26 10:21:50 2022 -0800 |
| tree | e82f3ba2d20509c2c8dbe29a6093405a0bc1c303 | |
| parent | e983e6521dd9cdd3fe56952e7d57f60b4bb4db5e [diff] |
Reject TE headers with values other than "trailers" in oghttp2. This CL improves oghttp2 spec compliance: https://httpwg.org/specs/rfc7540.html#n-connection-specific-header-fields In particular, the TE header field may only have the "trailers" value; otherwise the headers will be rejected as invalid. Http2RequestsTest.InvalidTeHeader with oghttp2: http://sponge2/6330792e-5128-4114-ab14-b99eeb73e17b PiperOrigin-RevId: 424381258
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.