RUST-2264 Fix handling of tlsInsecure in the URI #1453
Merged
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.
Fixes handling of the
tlsInsecure
option in a URI.tlsInsecure=bool
now setsTlsOptions::allow_invalid_certificates
andTlsOptions::allow_invalid_hostnames
(ifopenssl-tls
is enabled) to the value ofbool
.Note that
tlsInsecure
can only be set via a URI; theConnectionString
andClientOptions
types both store theTlsOptions
type, which only has fields for the more granular options.