Conversation
zeldrisho
marked this pull request as ready for review
September 21, 2026 05:08
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
1 participant
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.
The default HTTP configuration now preserves TLS certificate validation instead of disabling it for new installations. The explicit
DisableCertificateValidation=Truesetting remains available for compatibility when a user knowingly opts in.The legacy host callback now accepts a certificate only when .NET reports
SslPolicyErrors.None, avoiding unconditional acceptance while preserving the existing endpoint registration API. This protects translation traffic and configured API credentials from straightforward certificate interception without changing the selected translation providers or endpoints.