Skip to main content

Abort Ajax requests using jQuery


Using jQuery, how can I cancel/abort an Ajax request that I have not yet received the response from?



Source: Tips4allCCNA FINAL EXAM

Comments

  1. Most of the jQuery Ajax methods return an XMLHttpRequest (or the equivalent) object, so you can just use abort().

    See the documentation:


    abort Method (MSDN). Cancels the current HTTP request.
    abort() (MDC). If the request has been sent already, this method will abort the request.




    var xhr = $.ajax({
    type: "POST",
    url: "some.php",
    data: "name=John&location=Boston",
    success: function(msg){
    alert( "Data Saved: " + msg );
    }
    });

    //kill the request
    xhr.abort()


    UPDATE:
    As of jQuery 1.5 the returned object is a wrapper for the native XMLHttpRequest object called jqXHR. This object appears to expose all of the native properties and methods so the above example still works. See The jqXHR Object (jQuery API documentation).

    ReplyDelete
  2. It's an asynchronous request, meaning once it's sent it's out there.

    In case your server is starting a very expensive operation due to the AJAX request, the best you can do is open your server to listen for cancel requests, and send a separate AJAX request notifying the server to stop whatever it's doing.

    Otherwise, simply ignore the AJAX response.

    ReplyDelete
  3. You can't recall the request but you can set a timeout value after which the response will be ignored. See this page for jquery AJAX options. I believe that your error callback will be called if the timeout period is exceeded. There is already a default timeout on every AJAX request.

    ReplyDelete
  4. meouw's solution is correct, but if you're are interested in more control then you could try the Ajax Manager plugin for jQuery.

    ReplyDelete
  5. Save the calls you make on a array, then call xhr.abort() on each.

    HUGE CAVEAT: you can abort a request, but that only the clientside, the server side could still be running the request. If you are using something like PHP/ASP with session data, the session data is locked until the ajax has finished. So to allow the user to continue browsing the website, you have to call session_write_close().

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex