| commit | 9f32643a41437227add1a5804b87d554a6f22659 | [log] [tgz] |
|---|---|---|
| author | haoyuewang <haoyuewang@google.com> | Tue Jan 11 10:51:50 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 11 10:52:53 2022 -0800 |
| tree | 772ece71a1ac7b6790bed6a2afce0bb323df256b | |
| parent | acec624017b498c1bc931f5a9b23f486121f4382 [diff] |
Make GfeQboneServerSession buffer STREAM_FRAME (with pending stream) and drop MESSAGE_FRAME before LOAS authentication completes. Other stream related frames on the server side: STREAM_RESET_FRAME -> connection close STOP_SENDING_FRAME -> connection close WINDOW_UPDATE_FRAME is handled by pending stream before LOAS authentication completes. Other stream related frames on the client side: STREAM_RESET_FRAME -> connection close STOP_SENDING_FRAME -> connection close WINDOW_UPDATE_FRAME received before LOAS authentication -> connection close Protected by FLAGS_qbone_server_support_h3_loas. PiperOrigin-RevId: 421072604
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.