-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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.
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
HTTP3: Fix issue with GOAWAY handling and implement graceful shutdown logic in Http3LoopbackServer #56134
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsFixes #55025 Fix an issue where we are not properly handling a GOAWAY frame because we think we've seen one previously, even though we haven't. Add graceful shutdown logic to Http3LoopbackServer. Related QUIC tests and fixes.
|
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
src/libraries/System.Net.Quic/tests/FunctionalTests/QuicConnectionTests.cs
Outdated
Show resolved
Hide resolved
src/libraries/System.Net.Quic/tests/FunctionalTests/QuicConnectionTests.cs
Outdated
Show resolved
Hide resolved
src/libraries/System.Net.Quic/tests/FunctionalTests/QuicConnectionTests.cs
Show resolved
Hide resolved
…tion is closed/disposed, and related product fixes
…p3LoopbackConnection
472d07c
to
07a4c0a
Compare
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
I addressed the feedback -- please take a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Failures look unrelated |
Fixes #55025
Fixes #55508
Fix an issue where we are not properly handling a GOAWAY frame because we think we've seen one previously, even though we haven't.
Add graceful shutdown logic to Http3LoopbackServer.
Related QUIC tests and fixes.