| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
…ll to Custom Certificate Validation
|
Tagging subscribers to this area: @dotnet/ncl |
Sorry, something went wrong.
There was a problem hiding this comment.
Copilot reviewed 5 out of 7 changed files in this pull request and generated 1 comment.
Files not reviewed (2)
Sorry, something went wrong.
|
Approved via email by @SteveMCarroll on 5/7 |
Sorry, something went wrong.
|
/azp run runtime-libraries-coreclr outerloop |
Sorry, something went wrong.
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry, something went wrong.
|
/ba-g test failure is unrelated: #115359 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Backport of #111791 to release/9.0-staging
Customer Impact
Reported by customer (Identity team) - it was blocking their migration to WinHttpHandler and gRPC on .NET Framework (as first step of migration to .NET).
They reported slow performance due to creation of certificate chain in CertificateValidationCallback on each request.
This change caches certificate chain per connection as an opt-in feature (the default path is not affected).
They observed perf improvements on privates from %17.2 CPU to %0.61.
Regression
No - it was behaving this way since WinHttpHandler OOB package was introduced during .NET Core 1.0 shipping in 2016.
Testing
CI + Manual testing
Customer validated private bits against 9.0 servicing branch.
Risk
Low: This is under a feature switch (opt-in), it will not affect customers unless they enable the switch and opt-in into the feature.