Drop buffered metadata for a stream in ForgetStream().

This CL is a follow-up to a comment in cl/471086207
(http://screen/7SxFkVearSiZiaP), which pointed out that buffered metadata for a
stream may still be sent even after ForgetStream() for that stream is called on
the metadata manager.

In practice, this is unlikely to happen in production because pending metadata
is flushed at once for HTTP/2 [1] and will be flushed at once for HTTP/3 [2],
without intervening ForgetStream() calls, but this CL fixes ForgetStream() to
drop buffered metadata for the stream as a solid conceptual fix and in case
future changes allow intervening ForgetStream() calls in HTTP/2 or HTTP/3.

[1] e.g., http://google3/gfe/gfe2/vtl/vtl_client_dispatcher.cc;l=294-302;rcl=464844844
[2] e.g., cl/470321865

PiperOrigin-RevId: 472729185
1 file changed
tree: 9e39e41ad2159c96da8bb777758040e1bc424089
  1. build/
  2. quiche/
  3. .bazelrc
  4. BUILD.bazel
  5. CONTRIBUTING.md
  6. LICENSE
  7. README.md
  8. WHITESPACE
  9. 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.