| commit | 65f71e8bb0fcdb7f400af196d18a6a53a99a135c | [log] [tgz] |
|---|---|---|
| author | wub <wub@google.com> | Mon Jun 27 13:59:21 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 27 14:00:57 2022 -0700 |
| tree | ad1f4f008aedccef4de98775675f849b224e0547 | |
| parent | 3b91dad8e1c7166ff7faf153ee036e2209447f85 [diff] |
Automated g4 rollback of changelist 455516399. *** Reason for rollback *** Send a connection close in QuicDispatcher if a fatal TLS alert is raised while extracting CHLO. The only known such case is that when the SNI hostname contains a null byte, an 'unrecognized name' alert will be raised. This is the prerequisite for the rollback. *** Original change description *** Automated g4 rollback of changelist 455484069. *** Reason for rollback *** This is breaking GFE TAP builds. b/236320376 *** Original change description *** Fuzz SNI and ALPN in quic_tls_server_fuzz_test. *** *** Protected by FLAGS_quic_restart_flag_quic_dispatcher_send_connection_close_for_tls_alerts. PiperOrigin-RevId: 457560550
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.