| commit | 96b9ed6d4a1abcb776a07ac75e5fb017b07f53fb | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Tue Jan 25 08:56:53 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 25 09:00:02 2022 -0800 |
| tree | 187027b716faa97fab0c03de3a99551bbd5ba827 | |
| parent | ad700937b3b6d8fe46c3ff54be21c695f5baad92 [diff] |
Reject invalid :path values in oghttp2. This CL aligns oghttp2 more closely with the HTTP/2 spec WRT :path validation: https://httpwg.org/specs/rfc7540.html#rfc.section.8.1.2.3 In particular, the :path request pseudoheader must either begin with '/' or can be '*' for OPTIONS requests (note that oghttp2 performs this validation regardless of scheme). Http2RequestsTest.InvalidPathPseudoheaderExternalIp with oghttp2: http://sponge2/124d5146-d810-4416-8be9-db296b104a87 PiperOrigin-RevId: 424095088
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.