| commit | b159ae36aec18154f8de547be7637a024f58ca1c | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Tue Jul 12 11:38:34 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jul 12 11:40:15 2022 -0700 |
| tree | bbd3c51330ec3411c9db0435fa13916d29ee7b22 | |
| parent | dd4cd5eecd0506e7c29857ed7c1cd0fdfed7c0f7 [diff] |
Add BalsaVisitorInterface::OnHeader(). This method is called as soon as each header is parsed. This allows embedders to validate headers and potentially signal errors earlier. The motivation for this new method is Http1ServerConnectionImplTest.HeaderInvalidCharsRejection in Envoy, see https://sourcegraph.com/github.com/envoyproxy/envoy@4fd31f2/-/blob/test/common/http/http1/codec_impl_test.cc?L1115-1134. This test does not include the end of the header block, therefore BalsaVisitorInterface::ProcessHeaders() is never called. With this new method BalsaParser in Envoy will be able to validate the headers and make this test pass. PiperOrigin-RevId: 460514650
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.