Ignore and reset pushed streams.

This change only affects gQUIC. PUSH_PROMISE already triggers a connection close
when received over HTTP/3:
http://google3/third_party/quic/core/http/http_decoder.cc;l=193-197;rcl=542272544.

This change only affects client behavior. PUSH_PROMISE already triggers a
connection close when received by a server:
http://google3/third_party/quic/core/http/quic_spdy_session.cc;l=361-365;rcl=569300393

This change does two things: ignore pushed streams (this will allow removing a
lot of code), and reset the pushed stream (which might allow the server to save
some bandwidth).

This change should have no visible effect in any known QUICHE embedders.
Chromium and Envoy do not use gQUIC, and a certain legacy gQUIC client only
talks to servers that never push.

PiperOrigin-RevId: 570358476
2 files changed
tree: 998531ef7bc102362901e6c42b4fcd7d0360f062
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. BUILD.bazel
  6. CONTRIBUTING.md
  7. LICENSE
  8. README.md
  9. WHITESPACE
  10. WORKSPACE.bazel
README.md

QUICHE

QUICHE stands for QUIC, Http, 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.