Ajax: How to prevent jQuery from calling the success event after executing xmlHttpRequest.abort();

Question

Using jQuery's $.ajax() function. Wherether the request has been purposely aborted, or if the server is down (not responding) it appears the same outcome happens;

That is the "success" handler gets triggered where xmlHttpRequest.status = 0 and xmlHttpRequest.readyState = 4.

(I simulated the failed request by shutting off IIS, and then executing a xmlHttpRequest against the website that had been "turned off")

So my question is how can I determine the difference between an aborted request, or a request that genuinely failed due to the server not responding (because maybe the server is down), since both scenarios appear to give me the same status/readyState?

EDIT More accurately I want to know how to prevent calling the "success" handler after the .abort() function is called on ajax.

I have re-worded the question to reflect this.

Answer 1

You should set up an error handler, which will get called if the request fails. If you want to abort the request on the server, you could just return some value that you can check for in your success handler, or you could throw an exception from the server. jquery.ajax()

EDIT: You may want to look into this AJAX Queue/Cache/Abort/Block Manager v. 2.0 (link). It will allow you to run a function after a request has been aborted.

Answer 2

You could track aborts separately in a wrapper around xmlHttpRequest.abort.

Answer 3

When is abort called. I just tested in firebug console with the following

var req = $.ajax({url:"localaddress", success:function(){alert("evil");}}); req.abort();

ie abort right after the request, success isn't triggered.

Answer 4

I have come up with the following solution:

var request = $.ajax( /* ... */ );

// ...

request.onreadystatechange = function () {};
request.abort();

So, basically what I do, is to remove the success callback handler before calling abort().

This works like a charm.

Answer 5

I've noticed this same behavior, and request.onreadystatechange = function () {}; before calling .abort() does resolve the issue.