Fix for Kestrel's ParseHeaders throwing ArgumentOutOfRange exception #61316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

BrennanConroy merged 3 commits into dotnet:main from WereWind1:fix-parse-headers-exceptions

Apr 18, 2025

Merged

Fix for Kestrel's ParseHeaders throwing ArgumentOutOfRange exception #61316

Merge branch 'dotnet:main' into fix-parse-headers-exceptions

Azure Pipelines / aspnetcore-ci succeeded Apr 18, 2025 in 2h 15m 9s

Build #20250417.18 had test failures

0 errors / 1 warnings

Details

Failed: 2 (0.00%)
Passed: 222,121 (98.63%)
Other: 3,090 (1.37%)
Total: 225,213

Annotations

Check failure on line 1 in Microsoft.AspNetCore.Server.IIS.IISExpress.FunctionalTests.Http2Tests.Http2_RequestWithDataAndContentLength_Success

azure-pipelines / aspnetcore-ci

Microsoft.AspNetCore.Server.IIS.IISExpress.FunctionalTests.Http2Tests.Http2_RequestWithDataAndContentLength_Success

Test failed

Check failure on line 1 in Microsoft.AspNetCore.Mvc.FunctionalTests--net10.0.WorkItemExecution

azure-pipelines / aspnetcore-ci

Microsoft.AspNetCore.Mvc.FunctionalTests--net10.0.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

View more details on Azure Pipelines