Question

I use asynchronous XMLHttpRequest to call a function in ASP.net web service.
When I call an abort method on the XMLHttpRequest, after the server has received the request and processing it, the server continues processing the request.
Is there a way to stop the request processing on the server?

Answer 1

Generally speaking, no, you can’t stop the request being processed by the server once it has started. After all, how would the server know when a request has been aborted?

It’s like if you navigated to a web page but browsed to another one before the first one had loaded. That initial request will, at least to some extent (any client-side work will of course not take place), be fulfilled.

If you do wish to stop a long-running operation on the server, the service that is being invoked will need to be architected such that it can support being interrupted. Some psuedo code:

void MyLongRunningMethod(opId, args)
{
    work = GetWork(args)

    foreach(workItem in work)
    {
        DoWork(workItem)

        //Has this invocation been aborted?
        if(LookUpSet.Contains(opId))
        {
            LookUpSet.Remove(opId)
            return
        }
        //Or try this:
        if(Response.IsClientConnected)
        {
            HttpContext.Current.Response.End();
            return;
        }
    }
}

void AbortOperation(opId)
{
    LookUpSet[opId] = true
}

So the idea here is that MyLongRunningMethod periodically checks to see if it has been aborted, returning if so. It is intended that opId is unique, so you could generate it based on the session Id of the client appended with the current time or something (in Javascript, new Date().getTime() will get you the number of milliseconds since the epoch).

With this sort of approach, the server must maintain state (the LookUpSet in my example), so you will need some way of doing that, such as a database or just storing it in memory. The service will also need to be architected such that calling abort does not leave things in a non-working state, which of course depends very heavily on what it does.

The other really important requirement is that the data can be split up and worked on in chunks. This is what allows the service to be interruptable.

Finally, if some operation is to be aborted, then AbortOperation must be called – simply aborting the XMLHttpRequest invocation won’t do help as the operation will continue until completion.

Edit

From this question: ASP.Net: How to stop page execution when browser disconnects?

You could also check the Response.IsClientConnected property to try and determine whether the invocation had been aborted.

Generally speaking, the server isn’t going to know that a client has disconnected until it attempts to send data to it. See Best practice to detect a client disconnection in .NET? and Instantly detect client disconnection from server socket.