Allow specifying SNI separately from host address #300
Conversation
This file contains 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
When the target instance address cannot be resolved correctly from a hostname, but the SNI is still desirable for TLS verification and/or tenant selection reasons, provide a way to specify the SNI value via the `tls_server_name` (`EDGEDB_TLS_SERVER_NAME`) connection parameter.
fantix
approved these changes
Mar 14, 2024
MrFoxPro
pushed a commit
to MrFoxPro/edgedb-rust
that referenced
this pull request
Mar 27, 2024
When the target instance address cannot be resolved correctly from a hostname, but the SNI is still desirable for TLS verification and/or tenant selection reasons, provide a way to specify the SNI value via the `tls_server_name` (`EDGEDB_TLS_SERVER_NAME`) connection parameter.
MrFoxPro
pushed a commit
to MrFoxPro/edgedb-rust
that referenced
this pull request
Mar 27, 2024
When the target instance address cannot be resolved correctly from a hostname, but the SNI is still desirable for TLS verification and/or tenant selection reasons, provide a way to specify the SNI value via the `tls_server_name` (`EDGEDB_TLS_SERVER_NAME`) connection parameter.
MrFoxPro
pushed a commit
to MrFoxPro/edgedb-rust
that referenced
this pull request
Mar 27, 2024
When the target instance address cannot be resolved correctly from a hostname, but the SNI is still desirable for TLS verification and/or tenant selection reasons, provide a way to specify the SNI value via the `tls_server_name` (`EDGEDB_TLS_SERVER_NAME`) connection parameter.
MrFoxPro
pushed a commit
to MrFoxPro/edgedb-rust
that referenced
this pull request
Mar 28, 2024
When the target instance address cannot be resolved correctly from a hostname, but the SNI is still desirable for TLS verification and/or tenant selection reasons, provide a way to specify the SNI value via the `tls_server_name` (`EDGEDB_TLS_SERVER_NAME`) connection parameter.
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.
When the target instance address cannot be resolved correctly
from a hostname, but the SNI is still desirable for TLS verification
and/or tenant selection reasons, provide a way to specify the SNI value
via the
tls_server_name(EDGEDB_TLS_SERVER_NAME) connection parameter.