| commit | c97365c8d29acc056b7ba5cdbd78a6d0d4ef4bfb | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Thu Apr 11 15:43:04 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 11 15:44:21 2024 -0700 |
| tree | 42f7e0e6fd26d931ef80c3913fe7188bcf815483 | |
| parent | 4191e8be1c83f6e55b47d65593561807133dc83a [diff] |
Expose QUIC application/transport errors send/received on wire Chrome would want to access these wire values in order to generate more detailed Network Error Logging (NEL) reports. https://crrev.com/c/5445652 is a WIP CL that uses exposed values. Contexts: * https://chromium-review.googlesource.com/c/chromium/src/+/5400899/comment/7070d27f_f093857e/ * https://crbug.com/40715622 PiperOrigin-RevId: 623961927
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.