| commit | d6b44e11569f3daa581da01f9b4c1a90461b23c2 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Wed Sep 22 12:10:06 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 22 12:10:59 2021 -0700 |
| tree | ec547926690e4200b6d1f64f7cd43cd993a62b05 | |
| parent | fd8653ef8ff4e058a01e69783520374f1621ddf2 [diff] |
Plumb error code from QpackDecoder to QuicSpdyStream. Also, make QpackProgressiveDecoder::OnError() private. Also, change four string_view() constructors to testing::Eq() helpers in qpack_decoder_test.cc to be consistent with the other thirty EXPECT_CALLs. (Either one is sufficient, but compilation fails in Chromium when a C-style string literal is passed directly to EXPECT_CALL.) Protected by FLAGS_quic_reloadable_flag_quic_reject_invalid_chars_in_field_value. PiperOrigin-RevId: 398298181
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.