Skip to main content

How do I resend a failed ajax request?



I have multiple ajax requests some request data every minute others are initiated by the user through a ui.







$.get('/myurl', data).done(function( data ){

// do stuff..

});







The request might fail due to an authentication failure. I've setup a global .ajaxError() method for catching any failed requests.







$(document).ajaxError(function( e, jqxhr ){

// Correct error..

});







After I catch the error I reset authorization. Resetting the authorization works but the user has to manually re initiate the ajax call (through the ui).





How do I resend the failed request using the jqxhr originally sent?





(I'm using jQuery for the ajax)


Comments

  1. In this case, I would write a specific handler for the 403 status code, which means unauthorized (my server would return a 403 too). From the jquery ajax docs, you can do

    $.ajax({
    statusCode: {
    403: function() {
    relogin(onSuccess);
    }
    }
    });


    to achieve that.

    In that handler, I would call a relogin method, passing a function that captures what to do when login succeeds. In this case, you could pass in the method that contains the call you want to run again.

    In the code above, relogin should call the login code, and onSuccess should be a function that wraps the code you execute every minute.

    EDIT- based on your clarification in comment, that this scenario happens for multiple requests, I personally would create an API for your app that captures the interactions with the server.

    app = {};
    app.api = {};
    // now define all your requests AND request callbacks, that way you can reuse them
    app.api.makeRequest1 = function(..){..} // make request 1
    app.api._request1Success = function(...){...}// success handler for request 1
    app.api._request1Fail = function(...){...}// general fail handler for request 1

    /**
    A method that will construct a function that is intended to be executed
    on auth failure.

    @param attempted The method you were trying to execute
    @param args The args you want to pass to the method on retry
    @return function A function that will retry the attempted method
    **/
    app.api.generalAuthFail = function(attempted, args){
    return function(paramsForFail){ // whatever jquery returns on fail should be the args
    if (attempted) attempted(args);
    }
    }


    so with that structure, in your request1 method you would do something like

    $().ajax({
    ....
    statusCode: {
    403: app.api.generalAuthFail(app.api.request1, someArgs);
    }
    }}


    the generalAuthFailure will return a callback that executes the method you pass in.

    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