commit | acbdda4e4aa43e72a19aa72115b71e8eba57babb | [log] [tgz] |
---|---|---|
author | rch <rch@google.com> | Mon Apr 08 13:35:17 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Apr 08 13:36:06 2024 -0700 |
tree | a1d5bf01c65b3f8fd78cde8c9f20cf38ed6ae146 | |
parent | 2a464c5105053295611521d82a31bb123daf2281 [diff] |
Add DNAT support for QUIC Server Preferred Address. When a server is behind a DNAT, the address it receives packets on will be different from the address that the client sends to. So for QUIC Server Preferred Address the server needs to advertise a different address than the address it will expect to receive packets on. This change adds an an optional "expected" server preferred address to QuicConfig and changes QuicSession to pass the expected address to QuicConnection. Renames the QuicConnection member and method from "sent" to "expected". PiperOrigin-RevId: 622937854
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.