| commit | bda15bb16f0469c439b945589a1ec503178b19ec | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Fri Jan 21 09:15:29 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jan 21 09:16:10 2022 -0800 |
| tree | daf2e4e9c632c3f044ea0551adca24880073de5d | |
| parent | d072d377880775526b42f4b2ec9c6c4e995adb4f [diff] |
Reject 304 responses with bodies in oghttp2. This CL updates oghttp2 to track, based on a stream's headers, whether the stream can receive a body following those headers. That tracking is used to reject 304 responses with bodies in this CL and can be expanded to other scenarios (e.g., with other response codes or request methods) in the future. ProtocolIntegrationTest.304WithBody with oghttp2: http://sponge2/b1fcc5f6-9628-4579-b27b-25949278af8e PiperOrigin-RevId: 423337666
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.