Perf improvement: https

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| https | Json Https 13- Trends cobalt-hosted-lin | 08/06/2026 22:38:36 | 287,789 | 677,967 | 100.00 % (390,178) :thumbsup: | 2.45 σ | 159,237.60 | Changes NameVersionDiff Microsoft.AspNetCore.Antiforgery.dll `11.0.0-rc.1.26404.112` -> `11.0.0-rc.1.26406.108` https://github.com/dotnet/dotnet/compare/130b7a6f22566c06b7fca51913337eaca66adb5c...6c7fa710f4337334575f0c30f1691edc244518d1 Microsoft.AspNetCore.App `11.0.0-rc.1.26404.112` -> `11.0.0-rc.1.26406.108` https://github.com/dotnet/dotnet/compare/130b7a6f22566c06b7fca51913337eaca66adb5c...6c7fa710f4337334575f0c30f1691edc244518d1 Microsoft.NETCore.App `11.0.0-rc.1.26404.112` -> `11.0.0-rc.1.26406.108` https://github.com/dotnet/dotnet/compare/130b7a6f22566c06b7fca51913337eaca66adb5c...6c7fa710f4337334575f0c30f1691edc244518d1 |

[PowerBI Dashboard](https://aka.ms/aspnet/benchmarks)

@sebastienros

The issue only provides an HTTPS benchmark result and links to the PowerBI dashboard; it names no source files, tests, or entry points. Start by identifying the benchmark scenario and the change responsible for the reported result, then clarify the intended performance target and validation steps before attempting work.

Written by the indexing model from the issue text.