| commit | 754ded399dacfbd631bbde04116b7b573af5af41 | [log] [tgz] |
|---|---|---|
| author | dschinazi <dschinazi@google.com> | Fri Jul 11 13:16:45 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jul 11 13:17:44 2025 -0700 |
| tree | 680d6eef41e9ccc78ecb6db60a444c16774c5b01 | |
| parent | a321d386866ca3297461d96e58896e8de990020b [diff] |
Stop sending Host header in MASQUE HTTP/2 requests In HTTP/2, the `:authority` header is mandatory and the `host` header is optional. The only requirement is that, if `host` is included, it needs to match what's in `:authority`. So this code was doing something allowed by [the spec](https://www.rfc-editor.org/rfc/rfc9113#section-8.3.1-2.3.1), but some servers fail to process it. Since this is just a test client, we'll work around that issue by only sending `:authority`. PiperOrigin-RevId: 782086853
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.