| commit | 75f394c7cad61680ca13ccea019456a83f976d29 | [log] [tgz] |
|---|---|---|
| author | diannahu <diannahu@google.com> | Fri Mar 25 09:29:54 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 25 09:30:30 2022 -0700 |
| tree | e0092fea67b02dcb17f847779c134ca412b80e50 | |
| parent | dc5b8c00ee1602e2a77b7ac61c6259058820f258 [diff] |
Make oghttp2 reject connection-specific headers during header validation. Discovered while thinking about GFE3 behavior (rejecting these headers with nghttp2), thanks to ++pgal@'s investigation. This change brings oghttp2 into further alignment with nghttp2: - Request: http://google3/third_party/nghttp2/src/lib/nghttp2_http.c;l=203-209;rcl=436881423 - Response: http://google3/third_party/nghttp2/src/lib/nghttp2_http.c;l=283-289;rcl=436881423 PiperOrigin-RevId: 437266121
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.