Skip to main content

Non-ajax GET/POST using jQuery (plugin?)



This is one of those situations where I feel like I'm missing a crucial keyword to find the answer on Google...





I have a bag of parameters and I want to make the browser navigate to a GET URL with the parameters. Being a jQuery user, I know that if I wanted to make an ajax request, I would simply do:







$.getJSON(url, params, fn_handle_result);







But sometimes I don't want to use ajax. I just want to submit the parameters and get a page back.





Now, I know I can loop the parameters and manually construct a GET URL. For POST, I can dynamically create a form, populate it with fields and submit. But I'm sure somebody has written a plugin that does this already. Or maybe I missed something and you can do it with core jQuery.





So, does anybody know of such a plugin?





EDIT: Basically, what I want is to write:







$.goTo(url, params);







And optionally







$.goTo(url, params, "POST");





Source: Tips4all

Comments

  1. jQuery Plugin seemed to work great until I tried it on IE8. I had to make this slight modification to get it to work on IE:

    (function($) {
    $.extend({
    getGo: function(url, params) {
    document.location = url + '?' + $.param(params);
    },
    postGo: function(url, params) {
    var $form = $("<form>")
    .attr("method", "post")
    .attr("action", url);
    $.each(params, function(name, value) {
    $("<input type='hidden'>")
    .attr("name", name)
    .attr("value", value)
    .appendTo($form);
    });
    $form.appendTo("body");
    $form.submit();
    }
    });
    })(jQuery);

    ReplyDelete
  2. It is not clear from the question if you have a random bunch of values you want to pass on the querystring or is it form values.

    For form values just use the .serialize function to construct the querystring.

    e.g

    var qString = $('#formid').serialize();
    document.location = 'someUrl' + '?' + serializedForm


    If you have a random bunch of values you can construct an object and use the .param utility method.

    e.g

    var params = { width:1680, height:1050 };
    var str = jQuery.param( params );
    console.log( str )
    // prints width=1680&height=1050
    // document.location = 'someUrl' + '?' + str

    ReplyDelete
  3. Here's what I ended up doing, using the tip from redsquare:

    (function($) {
    $.extend({
    doGet: function(url, params) {
    document.location = url + '?' + $.param(params);
    },
    doPost: function(url, params) {
    var $form = $("<form method='POST'>").attr("action", url);
    $.each(params, function(name, value) {
    $("<input type='hidden'>")
    .attr("name", name)
    .attr("value", value)
    .appendTo($form);
    });
    $form.appendTo("body");
    $form.submit();
    }
    });
    })(jQuery);


    Usage:

    $.doPost("/mail/send.php", {
    subject: "test email",
    body: "This is a test email sent with $.doPost"
    });


    Any feedback would be welcome.

    Update: see dustin's answer for a version that works in IE8

    ReplyDelete
  4. FYI for anyone doing the doPost for rails 3, you need to add in the CSRF token, Adding the following to the answer should do that...

    var token = $('meta[name="csrf-token"]').attr('content');
    $("<input name='authenticity_token' type='hidden' value='" + token + "'/>").appendTo($form);

    ReplyDelete
  5. Yes. Excellent itsadok! That's just what I was looking for. I think that this non-ajax get and post functionality should be officially included in jquery. Thanks.

    ReplyDelete
  6. Good job itsadok! If you want a invisible form put it into hidden DIV:

    (function($) {
    $.extend({
    doGet: function(url, params) {
    document.location = url + '?' + $.param(params);
    },
    doPost: function(url, params) {
    var $div = $("<div>").css("display", "none");
    var $form = $("<form method='POST'>").attr("action", url);
    $.each(params, function(name, value) {
    $("<input type='hidden'>")
    .attr("name", name)
    .attr("value", value)
    .appendTo($form);
    });
    $form.appendTo($div);
    $div.appendTo("body");
    $form.submit();
    }
    });
    })(jQuery);

    ReplyDelete
  7. The accepted answer doesn't seem to cover your POST requirement, as setting document.location will always result in a GET request. Here's a possible solution, although I'm not sure jQuery permits loading the entire contents of the page like this:

    $.post(url, params, function(data) {
    $(document).html(data);
    }, "html");

    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