jQuery AJAX request failing in IE

Question

The following AJAX call is failing in IE.

$.ajax({
    url:"{{SITE_URL}}/content/twitter.json",
    dataType:"json",
    error:function(xhr, status, errorThrown) {
        alert(errorThrown+'\n'+status+'\n'+xhr.statusText);
    },
    success:function(json) {
               ...Snip...
    }
});

The error function returns

Undefined
parsererror
OK

No request is made to the server so I don't think its a problem with the JSON.

Fixed, See #1351389

It's working on other browsers? – Leandro Ardissone Jan 08 '09 at 20:53 — Leandro Ardissone, Jan 08 '09 at 20:53

score 51 · Accepted Answer · edited Oct 22 '13 at 11:32

51

Fixed, I changed the content-type from application/json; charset=utf8 to just plain application/json.
I hate IE :)

Also to avoid IE super-caching try this:

var d = new Date();
$.ajax({
        url:"{{SITE_URL}}/content/twitter.json?_="+d.getTime(), 
...Snip...

That way each request is a new url for IE to get :D

edited Oct 22 '13 at 11:32

informatik01

16,038
10
74
104

answered Aug 29 '09 at 13:02

Sam

5,416
7
47
49

27

God, am I glad I found this answer. This thing has cost me days of my life that Microsoft won't give me back. Just to reiterate: I effing hate IE, too. – Leonard Ehrenfried Nov 10 '09 at 21:11
14

Dear IE, I hate you. Dear @Sam, I love you. – Gabe Apr 26 '10 at 15:10
1

Also possible with jQuery.Ajax option "cache". http://api.jquery.com/jQuery.ajax/#options If set to false, it will force requested pages not to be cached by the browser. Setting cache to false also appends a query string parameter, "_=[TIMESTAMP]", to the URL. – John Korsnes Feb 02 '12 at 14:50
why set content-type just to `application/json`. is work? can you explain this..? – viyancs Mar 15 '12 at 02:44
1

Ie was getting hung up on the charset declaration – Sam Mar 15 '12 at 09:10
1

Thx for a solution! +1 for all IE haters – Vlad Dneprovskiy Apr 04 '12 at 10:34
Sam, I don't know who you are, but I think I love you. I spent over a day trying to figure out why IE wouldn't parse the JSON. Nowhere on the internet does it say that IE fails to do so if you include the charset. – Tommy Brunn Apr 12 '12 at 09:01
This also helps resolve every element on the page being selected if the AJAX call was aborted (not a success or error) – Ben Petersen Jun 11 '12 at 18:50

score 49 · Answer 2 · answered Jan 08 '09 at 23:50

49

For the caching problem why don't you simple use the cache: false parameter?

$.ajax({ 
    url: "yoururl",
    cache: false,
    ....

answered Jan 08 '09 at 23:50

tanathos

5,566
4
34
46

1

Cheers, solved it for me! I am curious as to why IE doesn't actually use the version that it caches... – Lea Hayes Nov 17 '11 at 16:44
Thanks, this saved me some confusion! Was working fine with Firefox, but not in IE. – Dave Baghdanov Sep 05 '12 at 17:47

score 8 · Answer 3 · answered Jan 08 '09 at 21:21

8

is this a copy/paste? the one thing that gets me all the time is leaving the last ',' in an object constructor. that is, most browsers JS accept:

o = { a:1, b:2, c:3, };

but IE chokes on this because the comma after the last item. change it to:

o = { a:1, b:2, c:3 };

and it works.

answered Jan 08 '09 at 21:21

Javier

60,510
8
78
126

Men - you are a freak :) You saved me alot time. Note that this breaks only IE7 and below. From IE8 this isn't rise errors. – bksi May 29 '12 at 00:12

score 7 · Answer 4 · answered Mar 26 '13 at 14:39

In newer versions of internet explorer (IE7) it is necessary to write the next line before calling $.ajax, otherwise it would never call the function:

$.ajaxSetup({ cache: false }); //this line before $.ajax!!!
$.ajax({
    //codes
    //codes
    //codes
});

score 4 · Answer 5 · answered Jan 08 '09 at 21:32

4

IE caches AJAX requests really aggressively (more so than Firefox, anyway). You need to set the Cache-Control headers in the response appropriately if this is not right for your site.

answered Jan 08 '09 at 21:32

Craig Stuntz

125,891
12
252
273

1

Good point, ive added ?_=1234 on the end of it and ie now request the page every time. Still same problem though :( – Sam Jan 08 '09 at 22:14

score 2 · Answer 6 · answered Jan 08 '09 at 22:18

2

One major problem with statically generated JSON and IE are the leading "commas", for examples this throws an error in IE:

{
    "one":"hello",
    "two":"hi",
 }

Note the last comma.

answered Jan 08 '09 at 22:18

Luca Matteis

29,161
19
114
169

score 0 · Answer 7 · answered May 07 '10 at 15:29

0

IE: JSON not defined error resolved at

http://funkatron.com/site/comments/safely-parsing-json-in-javascript/

by using dataType: "json" and avoid parsing

answered May 07 '10 at 15:29

user333483

1

score 0 · Answer 8 · answered Jan 08 '09 at 21:32

0

What is the {{SITE_URL}} chunk giving is about. Try looking at the code in view source code of the browser. If the {{SITE _URL}} chunk has a trailing slash and that would make the request url:

http://modomain.com//content/twitter.json

Which could creep IE out?

answered Jan 08 '09 at 21:32

Pim Jager

31,965
17
72
98

Well, any browser I know of woudl creep out about that... so this is no specific IE problem. – SamiSalami Aug 31 '12 at 12:35

jQuery AJAX request failing in IE

8 Answers8

Linked