Will Kestrel cancel the request immediately

when there are many requrest in the queue, and some user may refresh or stop in the browse when website is slow, if kestrel not cancel the request immediately, that will make site much slower, I know there is CancelationToken I can use to cancel the action immediately , but I may not use CancelationToken everywhere, I know Thread can Abort() , but in asp.net core seems there are Tasks , and I don’t know how to cancel a Task immediately.

so my question is will “kestrel” or “asp.net core’s HttpContext” abort the request immediately when connection reset

[Eilon]

How other systems handle connection resets is not particularly relevant because ASP.NET Core is not any of those systems (and shares almost nothing with any of them).

The idea is that if you already know your code is “safe” for Thread.Abort, you might as well write your code cooperatively anyway (such as by using cancellation tokens).

I found a few links discussing Thread.Abort and how to safely stop code from running:

• https://blogs.msmvps.com/senthil/2008/12/17/the-dangers-of-thread-abort/
• https://stackoverflow.com/questions/1559255/whats-wrong-with-using-thread-abort
• https://haacked.com/archive/2004/11/12/how-to-stop-a-thread.aspx/
• http://www.windowsdevcenter.com/pub/a/dotnet/2003/02/18/threadabort.html

[aspnet-hello]

We periodically close ‘discussion’ issues that have not been updated in a long period of time.

We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.