-
Notifications
You must be signed in to change notification settings - Fork 5.1k
[HTTP3] Correctly handle server closing a control stream #73680
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] Correctly handle server closing a control stream #73680
Conversation
Tagging subscribers to this area: @dotnet/ncl Issue DetailsThis PR makes sure we behave according to the spec when server closes/aborts either its or clients control stream (i.e. close the connection with
|
/azp run runtime-libraries-coreclr outerloop |
Azure Pipelines successfully started running 1 pipeline(s). |
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, thanks.
src/libraries/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/Http3Connection.cs
Outdated
Show resolved
Hide resolved
…andler/Http3Connection.cs Co-authored-by: Marie Píchová <11718369+ManickaP@users.noreply.github.com>
@@ -7,6 +7,7 @@ | |||
using System.Runtime.Versioning; | |||
using System.Net.Quic; | |||
using System.IO; | |||
using System.Linq; |
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.
using System.Linq; |
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.
oops, I missed this one and merged it, I will remove it when I next touch HTTP3
This PR makes sure we behave according to the spec when server closes/aborts either its or clients control stream (i.e. close the connection with
H3_CLOSED_CRITICAL_STREAM
error)