Comments on: jQuery.getJSON()

By: dblrbl

dblrbl — Fri, 19 Mar 2010 22:19:05 +0000

Try setting server header: 'Cache-Control: no-cache, must-revalidate'
If you don't have server access you can trick the browser to not cache the page by appending a timestamp to the end of the URL: http://server.com/?json=true&21334342134

By: Steven Wright

Steven Wright — Fri, 19 Mar 2010 15:17:06 +0000

My understanding is that the callback only fires if the request succeeds. But in the following case it actually appears to be firing before the request returns. If dump json to the console it is undefined. If fetch that URL with a browser it returns the json, but it takes a while. Is there a timeout of some sort?

// Get the Subscriber Id
var s = new Date();
$.getJSON(service_url + 'get_subscriber_id', {
mac_address: mac_address,
ts: s.getTime()
}, function(json){
url_params.subscriber_id = json.SubscriberId;
$.get_callerid_history();
});

By: dev

dev — Fri, 19 Mar 2010 12:56:57 +0000

I would like to send an array along when using getJSON, is this possible? Something like this:

$.getJSON("http://localhost/ci_pbbg/universe/tile", {'mapTiles[]' : mapTiles}, function(data){...

The {'mapTiles[]' : mapTiles} bit works when used as data in load, but not in getJSON. Any clue how I can send an array along with this?

By: Karl Swedberg

Karl Swedberg — Thu, 18 Mar 2010 14:25:09 +0000

Hi Mike,

I just updated the entry. Let me know if it's satisfactory now.

By the way, your version of the history of JSON isn't really accurate.

By: mike nelson

mike nelson — Wed, 17 Mar 2010 18:29:12 +0000

Hi Karl, can you please update the documentation to specifically point out the change between jQuery 1.3.x and 1.4.x which tightens up on the json format. Specifically call out the two major gotchas (1) requiring double quotes instead of single quotes, and (2) even property names need quoting eg { success: true } should now be { “success”: true }.

Although some dudes went off and “standardised” the json format the rest of us thought it was exactly what it said on the tin – javascript object notation – ie any valid javascript object syntax would be valid. So I am sure many people have this same problem and as you point out it fails silently so this is going to be a common pitfall.

By: Keo

Keo — Wed, 20 Jan 2010 17:52:15 +0000

For others that might be having trouble with the recent strict changes this {Animal:”DOG”,Name:”Fido”} must now be {“Animal”:”DOG”,”Name”:”Fido”}.
Notice the extra quotes around the field names now that are required.