.Net: Remove the HTTPS validations in AzureClientCore#11943
Merged
markwallace-microsoft merged 2 commits intomicrosoft:mainfrom May 19, 2025
Merged
.Net: Remove the HTTPS validations in AzureClientCore#11943markwallace-microsoft merged 2 commits intomicrosoft:mainfrom
markwallace-microsoft merged 2 commits intomicrosoft:mainfrom
Conversation
* Remove HTTPS validation from `AzureClientCore` class. * We are redirecting requests internally to inject API keys securely and keep track of token usage in a transparent way, but this involves a YARP proxy in between certain applications and Azure OpenAI. That proxy, being internal behind our servers, doesn't use HTTPS and it doesn't need to use it either. The current version of Semantic Kernel throws an error when using a HTTP endpoint. Current fixes involve a lot of additional steps and going out of the server to come back in through our azure gateway or adding self-generated certificates and bypassing SSL errors, etc... This fix would be very helpful. * Remove the `Verify.StartsWith` validation for the `endpoint` parameter in the constructors of `AzureClientCore` class. * Remove the test case `ConstructorWithInvalidEndpointShouldThrowArgumentException` from `AzureClientCoreTests` class. * Ensure the remaining test cases do not enforce HTTPS validation.
rogerbarreto
approved these changes
May 13, 2025
markwallace-microsoft
approved these changes
May 13, 2025
Contributor
Author
|
@microsoft-github-policy-service agree |
Contributor
Author
|
Hey guys! There seems to be a random unrelated error in the pipelines. I updated the branch to see if it helped, not sure if it requires a re-approval.
|
markwallace-microsoft
approved these changes
May 19, 2025
jcruzmot-te
pushed a commit
to thousandeyes/aia-semantic-kernel
that referenced
this pull request
Sep 15, 2025
### Remove HTTPS validation from `AzureClientCore` class. We are redirecting requests internally to inject API keys securely and keep track of token usage in a transparent way, but this involves a YARP proxy in between certain applications and Azure OpenAI. That proxy, being internal behind our servers, doesn't use HTTPS and it doesn't need to use it either. The current version of Semantic Kernel throws an error when using a HTTP endpoint. Current fixes involve a lot of additional steps and going out of the server to come back in through our azure gateway or adding self-generated certificates and bypassing SSL errors, etc... This fix would be very helpful. * Remove the `Verify.StartsWith` validation for the `endpoint` parameter in the constructors of `AzureClientCore` class. * Remove the test case `ConstructorWithInvalidEndpointShouldThrowArgumentException` from `AzureClientCoreTests` class. * Ensure the remaining test cases do not enforce HTTPS validation.
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
3 participants
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.
Remove HTTPS validation from
AzureClientCoreclass.We are redirecting requests internally to inject API keys securely and keep track of token usage in a transparent way, but this involves a YARP proxy in between certain applications and Azure OpenAI. That proxy, being internal behind our servers, doesn't use HTTPS and it doesn't need to use it either. The current version of Semantic Kernel throws an error when using a HTTP endpoint. Current fixes involve a lot of additional steps and going out of the server to come back in through our azure gateway or adding self-generated certificates and bypassing SSL errors, etc... This fix would be very helpful.
Verify.StartsWithvalidation for theendpointparameter in the constructors ofAzureClientCoreclass.ConstructorWithInvalidEndpointShouldThrowArgumentExceptionfromAzureClientCoreTestsclass.