Sunday, May 19, 2024
 Popular · Latest · Hot · Upcoming
rated 0 times [  42] [ 2]  / answers: 1 / hits: 19451  / 12 Years ago, fri, october 12, 2012, 12:00:00

My Ajax cross domain request is failing in IE 9 with Access denied. I have read through several posts regarding this topic, and AFAIK it should work.

  1. IE9 and jQuery 1.8.1

  2. Call is async, jsonp and crossdomain, cache is false. These are the prerequisites I have found.

  3. Works in latest Firefox and Chrome.

  4. is true

  5. Even the response header is set: Access-Control-Allow-Origin:* (SO)

  6. The returned JSON code would also be correct, have used a checker (also see 3.)

So why is this failing with Access denied? Any idea? Could it be because my code is called from within a JavaScript library, and not a <script></script> tag on the page?

What am I missing?

    // The code is part of an object's method (prototype)
// code resides in a library Mylib.js

type: 'GET',
url: url,
cache: false,
async: true,
crossdomain: true, // typo, crossDomain, see my answer below
datatype: jsonp, // dataType
success: function (data, status) {
if (status == success && !Object.isNullOrUndefined(data)) { ... }

error: function (xhr, textStatus, errorThrown) {
// access denied

-- Edit -- based on Robotsushi's comments, some further research ---

  1. Indeed, cannot find XDomainRequest in the jQuery source code (1.8.1)

  2. If I do not set cors ( = true) I'll end up with a No Transport exception.

  3. Still wondering why others obviously succeed with IE9 cross domain requests, e.g. here: jQuery Cross-Domain Ajax JSONP Calls Failing Randomly For Unknown Reasons In Some IE Versions

  4. The way jQuery handles this, seems to be around the code below, but this is not called in my particular case, no idea why?

    // Bind script tag hack transport
    jQuery.ajaxTransport( script, function(s) {

    // This transport only deals with cross domain requests
    if ( s.crossDomain ) {

  5. A similar situation here in year 2010: Jquery $.ajax fails in IE on cross domain calls However, this should have been solved by the later jQuery versions.

More From » jquery


Ok, working now. Couple of mistakes on my side:

  1. It is crossDomain: true, dataType: jsonp , typo - missed capital letters.

  2. JSONP requests are not transparent. The data are not simply JSON notation, but have to be wrapped in a Js function call (on the server side): see Basically this means, if you cannot modify the sent data, JSONP is not the right option for you.

All things considered, it works. So my personal checklist would be:

  1. Use json if possible (e.g. with Chrome, FF, or most likely IE10). Make sure response header is set: Access-Control-Allow-Origin:*

  2. If using jsonp, check: async: true, jsonp and crossdomain: true, cache is false, is true These are the prerequisites I have found.

  3. Also make sure the jsonp response is a function call (JSON wrapped in function), not just ordinary JSON data.

[#82583] Thursday, October 11, 2012, 12 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.

Total Points: 737
Total Questions: 104
Total Answers: 89

Location: Andorra
Member since Sat, May 27, 2023
1 Year ago