Avoid validating content-length values for 304 responses in oghttp2.

According to https://httpwg.org/specs/rfc7230.html#rfc.section.3.3.2, a server
may send the content-length header in a 304 response, which does not have a
body. The content-length header in this case indicates the body length the
server would have sent in the corresponding 200 response. Therefore, this CL
updates oghttp2 to not check for received content-length header value mismatch
in 304 responses. This update is important for several integration test cases.

PiperOrigin-RevId: 422905007
3 files changed
tree: b22dd4a778d06e724277d827ac7dedf362301a51
  1. common/
  2. epoll_server/
  3. http2/
  4. quic/
  5. spdy/
  8. README.md


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.