| commit | 2f10941b814348cf0a428ab856f03399253ad73e | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Tue Sep 13 15:11:58 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Sep 13 15:13:54 2022 -0700 |
| tree | f90f3bc87699569aca8c7dadd6bf303742c2c5a2 | |
| parent | 43bc4bf6a49c3f27f3d1ca05492a885df2b3f513 [diff] |
Test that Http2HeaderBlock order is preserved. This is to test that Http2HeaderBlock does not have any magic to reorder headers, for example, to move pseudo-header fields before regular ones for spec compliance. In contrast, note that HpackEncoder moves pseudo-headers to the beginning of the header block when encoding. PiperOrigin-RevId: 474136110
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.