Repository navigation
Add an async SNI example - #204
Merged
Merged
Conversation
Show how to resolve a TLS certificate asynchronously from the ClientHello with `LazyConfigAcceptor` and a custom `Accept` implementation. The built-in acceptor picks one config up front and `from_sni_pem_files` covers a known hostname map, but a resolver that has to await needs this pattern. The example shares one deadline across the ClientHello read and the handshake, sets ALPN through `RustlsConfig::from_pem_file`, and rejects unknown or missing server names.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
examples/async_sni.rs, which resolves a TLS certificate asynchronously from the server name in the ClientHello, after the ClientHello is read but before the rest of the handshake. No library code changes.This answers the request in the tracked issue (#85). The built-in
RustlsAcceptorpicks oneServerConfigup front, andRustlsConfig::from_sni_pem_files(0.9.0) covers a map of known hostnames, but a resolver that has to await — a database, a secret manager, an ACME directory — needstokio_rustls::LazyConfigAcceptorinside a customAcceptimpl. That path exists today but was undocumented.