| commit | fa871a9408c96e361fee695b58daf0db9d4baa1d | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Wed Jun 21 09:03:44 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jun 21 09:04:37 2023 -0700 |
| tree | a0ab65c0c8d9b48a8281b33e059a29937a2e53a6 | |
| parent | 166f8ac5a0332c1f200fa24c4edcef4600e9b215 [diff] |
Enforce that WEBTRANSPORT_STREAM is always sent at the beginning of the stream if draft-07 or later is used. This also fixes the way parsing WEBTRANSPORT_STREAM is enabled. Currently, we enable it iff the local peer is willing to use WebTransport (which is incorrect). After this CL, the code follows the following (correct and tested) logic: 0. Always wait for peer SETTINGS to be available. 1. If WebTransport is not supported, WEBTRANSPORT_STREAM is treated as a regular frame. 2. If WebTransport is at draft-02, WEBTRANSPORT_STREAM can occur at any position of the stream. 3. If WebTransport is at draft-07 or later, WEBTRANSPORT_STREAM can only occur at the beginning of the stream. PiperOrigin-RevId: 542272544
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.