| commit | 43d4f0a6b822c9ba144577338bd6a3728ad79975 | [log] [tgz] |
|---|---|---|
| author | danzh <danzh@google.com> | Thu Nov 04 13:17:08 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 04 13:18:02 2021 -0700 |
| tree | 3d5394bf4ff083df27b7eaf2bacad0b2cee9b379 | |
| parent | e286d006cb463ffb24447b350a0b706fe68bcea5 [diff] |
Validate QUIC request/response headers against invalid token and disallowed headers. Add empty string to disallow-list. Split --gfe2_reloadable_flag_quic_verify_request_headers into 2 flags: --gfe2_reloadable_flag_quic_verify_request_headers_2 to validate QUIC request/response headers against invalid request with ratio monitoring; mark H2 request with empty string header as invalid earlier in H2 stack. --gfe2_reloadable_flag_quic_act_upon_invalid_header return error response upon any invalid QUIC request header. Protected by quic_reloadable_flag_quic_verify_request_headers_2 and quic_reloadable_flag_quic_act_upon_invalid_header. PiperOrigin-RevId: 407654730
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.