Perf improvement: antiforgery-noop, https, mvc

| Scenario | Environment | Date | Old RPS | New RPS | Change | Deviation | StDev | Dependencies |
| -------- | ----------- | ---- | ------- | ------- | ------ | --------- | ----- | ------------ |
| antiforgery-noop | Antiforgery No Operation 8- Trends gold-lin | 06/28/2026 13:41:57 | 1,542,646 | 1,567,579 | 1.62 % (24,932) :thumbsup: | 2.43 σ | 10,273.45 | Changes NameVersionDiff Microsoft.AspNetCore.Antiforgery.dll `11.0.0-preview.7.26325.123` -> `11.0.0-preview.7.26327.102` https://github.com/dotnet/dotnet/compare/354f8b358deba86fa37d9fca5ad80a87ac4853f3...3e328deefbd3029c2f957050c508b4faeee3d71f Microsoft.AspNetCore.App `11.0.0-preview.7.26325.123` -> `11.0.0-preview.7.26327.102` https://github.com/dotnet/dotnet/compare/354f8b358deba86fa37d9fca5ad80a87ac4853f3...3e328deefbd3029c2f957050c508b4faeee3d71f Microsoft.NETCore.App `11.0.0-preview.7.26325.123` -> `11.0.0-preview.7.26327.102` https://github.com/dotnet/dotnet/compare/354f8b358deba86fa37d9fca5ad80a87ac4853f3...3e328deefbd3029c2f957050c508b4faeee3d71f |
| https | Json Https 14- Trends cobalt-hosted-lin-azl3-28 | 06/28/2026 22:52:26 | 299,753 | 391,266 | 30.53 % (91,513) :thumbsup: | 4.20 σ | 21,783.76 | Changes NameVersionDiff Microsoft.AspNetCore.Antiforgery.dll `11.0.0-preview.7.26326.101` -> `11.0.0-preview.7.26328.102` https://github.com/dotnet/dotnet/compare/e8cf72e05e4866224daa6b959d1f44a810dc0606...7c528f6e19c5245206de3dc561eb8a110bf9f746 Microsoft.AspNetCore.App `11.0.0-preview.7.26326.101` -> `11.0.0-preview.7.26328.102` https://github.com/dotnet/dotnet/compare/e8cf72e05e4866224daa6b959d1f44a810dc0606...7c528f6e19c5245206de3dc561eb8a110bf9f746 Microsoft.NETCore.App `11.0.0-preview.7.26326.101` -> `11.0.0-preview.7.26328.102` https://github.com/dotnet/dotnet/compare/e8cf72e05e4866224daa6b959d1f44a810dc0606...7c528f6e19c5245206de3dc561eb8a110bf9f746 |
| mvc | Json Mvc 14- Trends cobalt-hosted-lin-azl3-28 | 06/28/2026 22:53:50 | 311,491 | 432,117 | 38.73 % (120,626) :thumbsup: | 4.09 σ | 29,463.68 | Changes NameVersionDiff Microsoft.AspNetCore.Antiforgery.dll `11.0.0-preview.7.26326.101` -> `11.0.0-preview.7.26328.102` https://github.com/dotnet/dotnet/compare/e8cf72e05e4866224daa6b959d1f44a810dc0606...7c528f6e19c5245206de3dc561eb8a110bf9f746 Microsoft.AspNetCore.App `11.0.0-preview.7.26326.101` -> `11.0.0-preview.7.26328.102` https://github.com/dotnet/dotnet/compare/e8cf72e05e4866224daa6b959d1f44a810dc0606...7c528f6e19c5245206de3dc561eb8a110bf9f746 Microsoft.NETCore.App `11.0.0-preview.7.26326.101` -> `11.0.0-preview.7.26328.102` https://github.com/dotnet/dotnet/compare/e8cf72e05e4866224daa6b959d1f44a810dc0606...7c528f6e19c5245206de3dc561eb8a110bf9f746 |

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

@sebastienros

Start by reviewing the reported antiforgery-noop, https, and mvc benchmark results and the linked PowerBI Dashboard. No source files or tests are identified in the issue, so determine which ASP.NET Core area should change and define a repeatable benchmark-based completion criterion before starting implementation.

Written by the indexing model from the issue text.