-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Wait to dispose CTS for IIS #9389
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
This will also address some gaps we had between Kestrel and IIS, specifically not cancelling the cts after writing the entire content and checking content length. |
src/Servers/IIS/IIS/src/Core/IISHttpContext.IHttpRequestLifetimeFeature.cs
Outdated
Show resolved
Hide resolved
src/Servers/IIS/IIS/src/Core/IISHttpContext.IHttpRequestLifetimeFeature.cs
Outdated
Show resolved
Hide resolved
File an issue for creating a LazyResettableCts type so we can backlog it 😉 |
Debugging the inproc failure with NTLM tests. Seems like there was a failed request. |
Figured it out, bad check for requestAborted. |
src/Servers/IIS/IIS/src/Core/IISHttpContext.IHttpRequestLifetimeFeature.cs
Outdated
Show resolved
Hide resolved
@javiercn https://dev.azure.com/dnceng/public/_build/results?buildId=157804 |
Never seen that one before. |
That's in SignalR (cc @mikaelm12) Doesn't seem like something we can control... |
Fixes #4422
Fixes https://github.com/aspnet/AspNetCore-Internal/issues/1831
Still have a few tests I need to write. Will mark ready for review when appropriate.
@halter73 I lightly explored making a helper for safe disposal/cancellation, and it didn't look great. I'm going to keep them separate for now.