| commit | 770a8a36f6047902a6a5acf8bfa785ba60674c06 | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Mon Mar 04 14:07:00 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 04 14:07:55 2024 -0800 |
| tree | 1bfd059f4328446145aef72df4c4ad5548d5d840 | |
| parent | 1bf8322a2aad50c5fcfef3aad537d1f2a9377154 [diff] |
Switch moqt_messages.h types to use std::string instead of absl::string_view The immediate goal here is to fix a use-after-free caused by the fact that MoqtSession::active_subscriptions_ contains a bunch of MoqtSubscription objects that have views to potentially deleted track names (`blaze test -c dbg --config=asan //third_party/quic/moqt/...` will reproduce those). The long-term goal is to make moqt_messages.h types safer to use, as they're really prone to UAFs right now. PiperOrigin-RevId: 612578165
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.