commit | 3abbc177eef9c6de46f57fb69776a83f04902a02 | [log] [tgz] |
---|---|---|
author | dschinazi <dschinazi@google.com> | Mon Jan 06 09:06:34 2025 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 06 09:07:19 2025 -0800 |
tree | 8aae40ec18618a76d3d614a84992883eb1b10c8e | |
parent | 3a31e4df00d298ef13a881e80f876b43300ba11c [diff] |
Officially allow out-of-order writes in QuicStreamSendBuffer This has always worked, but there was a QUIC_BUG to prevent it. Unfortunately the QUIC_BUG had a bug where QuicStreamSendBuffer::current_end_offset_ was not computed properly, so it never correctly enforced in-order writes. Chaos Protection v2 triggers this QUIC_BUG when the Client Hello size exceeds the value of the quic_send_buffer_max_data_slice_size flag. PiperOrigin-RevId: 712548578
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.