Avoid OnInvalidFrame() to make content-length errors stream-level in oghttp2.

As background, cl/422597021 made oghttp2 follow nghttp2 on calling the visitor
OnInvalidFrame() to make an integration test pass with a connection-level error
expectation [1], but another test expects a stream-level error instead [2].

These tests both pass with nghttp2 because nghttp2 handles content-length
differently based on whether the end_stream frame is headers/trailers vs.  data
(see cl/422597021 description for details). However, preferred behavior is for
content-length errors to be stream-level across the board.

This CL updates oghttp2 such that content-length errors do not call
OnInvalidFrame() and are thus stream-level, for both tests. The expectations in
[1] will be changed to align with HTTP/3.


PiperOrigin-RevId: 422833845
4 files changed
tree: 14a773ac7707ac4581c8ea11ca2b3a42f1ac88f8
  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.