Ignore incoming HTTP/3 MAX_PUSH_ID frames.

Do not call Http3DebugVisitor::OnMaxPushIdFrameReceived().  This is not
implemented in the server, and is always an error in Chrome (because a server is
not allowed to send such a frame), and therefore will be visible in Chrome's
NetLog when the stream is reset.

Do not call QuicSpdySession::OnMaxPushIdFrame().  This removes the enforcement
on the values in successive MAX_PUSH_ID frames, but will allow us to remove some
complexity from QuicSpdySession when the flag is deprecated.

The enforcement on frame types (MAX_PUSH_ID is not allowed on any stream other
than the control stream, it cannot be sent by the server, it cannot be the first
frame on the control stream) is still in place.

PiperOrigin-RevId: 431034537
3 files changed
tree: 5610485c0527ed20e00e185bbc2693a67ab72625
  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.