Conversation
…ams_KnownHeaderReused Associated issue: #aw_http2rhr Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
bot
requested review from
BrennanConroy and
halter73
as code owners
github-actions
bot
added
test-failure
area-networking
This was referenced Mar 23, 2026
wtgodbe
approved these changes
Mar 23, 2026
wtgodbe
deleted the
quarantine/http2-request-header-reuse-316a68ae5fa844d5
branch
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
1 participant
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.
Quarantines
Microsoft.AspNetCore.Server.Kestrel.Core.Tests.Http2ConnectionTests.RequestHeaderStringReuse_MultipleStreams_KnownHeaderReusedwhich has been failing flakily in CI.The test asserts that
ContentTypeheader string instances are reused across multiple HTTP/2 streams (expected count=1), but flakily sees count=0. This is a timing-sensitive check on internal header string interning behavior.The test has failed 2 times across 2 separate builds in the past 30 days.
Associated issue: #65915