Wrong additional parameters in $.ajax

Question

I'm trying to call a web service to get some data. I need pass this URL in a GET method:

http://localhost/ecosat/ws/api.php?t=vw_motorista

But, when I look in Chrome Developer Tools, the link is:

http://localhost/ecosat/ws/api.php?t=vw_motorista&_=1397500899753

I'm not passing this parameter: &_=1397500899753

With this additional parameter, I received a 500 error. I can't change the web service to handle this.

What's going on? Is Chrome is changing my code?

This my Ajax

function get(pURL, pToken) {
    var ret = null;

    $.ajax({
        type: "GET",
        dataType: "json",
        async: false,
        timeout: globalTimeOut,
        cache: false,
        url: pURL,
        headers: {"Token": pToken},
        error: function(request, status, error) {
            ret = null;
        },
        success: function(data) {
            ret = data;
        }
    });
    return ret;
}

you'll need to show us your code before we can diagnose it. A fiddle would be nice — Stephen Thomas, Apr 14 '14 at 18:51
Make sure cache : false. jQuery automatically adds a timestamp to the end of the URL for you, making sure that ajax requests are never cached when we use cache: true — Tushar, Apr 14 '14 at 18:52
@Tushar it's the other way around: `cache: false` adds the `_` param, `cache: true` doesn't. — cmbuckley, Apr 14 '14 at 18:54
Yes, got confused, just remove the cache parameter if you dont need it — Tushar, Apr 14 '14 at 18:55

score 1 · Accepted Answer · edited May 23 '17 at 12:13

1

You're probably using cache: false setting in your ajax query. It adds a _ parameter with a timestamp value, to make sure that your ajax call doesn't get cached by the browser.

Remove this setting, if you don't need it. But if you need make sure caching is disabled, you could try two things:

add your own parameter with a timestamp to your query, e.g. {ts: new Date.getTime()}, or

if possible, add headers to the web server response. See this question

edited May 23 '17 at 12:13

Community

1
1

answered Apr 14 '14 at 18:51

keune

5,779
4
34
50

Please explain what should the OP do instead. – Sumner Evans Apr 14 '14 at 18:55
Why would him adding his own parameter instead of using the cache property be any different? – Kevin B Apr 14 '14 at 19:07
maybe it was the underscore character that caused the problem on the server side, so i thought trying a parameter with a different name could work. of course i'm just guessing. – keune Apr 14 '14 at 19:09
i change the cache option to true and works fine. Many thanks – Vitor Villar Apr 14 '14 at 19:52

Wrong additional parameters in $.ajax

1 Answers1