-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Close accept loop when closing connection #44885
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
Conversation
|
Tagging subscribers to this area: @dotnet/ncl Issue Details
|
src/libraries/System.Net.Quic/src/System/Net/Quic/Implementations/MsQuic/MsQuicConnection.cs
Outdated
Show resolved
Hide resolved
3351d86 to
f0fa27f
Compare
|
Verified this works locally. |
|
There are other issues I'm hitting locally, but will investigate in another PR. |
src/libraries/System.Net.Quic/src/System/Net/Quic/Implementations/MsQuic/MsQuicListener.cs
Show resolved
Hide resolved
src/libraries/System.Net.Quic/src/System/Net/Quic/Implementations/MsQuic/MsQuicListener.cs
Outdated
Show resolved
Hide resolved
…ons/MsQuic/MsQuicListener.cs Co-authored-by: Stephen Halter <halter73@gmail.com>
Found when working on dotnet/aspnetcore#26638 in the aspnetcore repo.
When closing the connection by a call to CloseAsync, it makes sense to force the accept loop to close. Other scenarios like Abort from client and Abort from transport already close the channel.