Javascript SDK Internet Explorer, JSON requests failing

I'm unable to send requests from the javascript SDK to ACS with Internet Explorer. In Chrome, Firefox, Safari and Opera the same code works fine.

In using jQuery 1.6.3 in combination with 1.2 cocoafish. I've also tried jQuery 1.8.2

For testing purposes I use the reset password :

var data = {
   email: email,
   template:'reset'
};
 
sdk.sendRequest('users/request_reset_password.json', 'GET', data, callback);
function callback(data) {
     alert(data.meta);
}

IE7 and 8 give me this error : SCRIPT438: Object doesn't support this property or method cocoafish-1.2.min.js, line 1 character 261

IE9 doesn't really give any feedback. It calls the callback but the meta data is undefined.

Any tips or tricks?

I've tried a clean json call, but didn't function either. Could it be some header/caching issue?

Total stab in the dark, but could it be something to do with JSON.parse/stringify functions? I'm pretty sure you need to include JSON2.js first for IE, from here: douglascrockford / JSON-js

Thanks for the answer. My issue started quite fuzzy, but it's getting clearer now. I was testing locally.. and all browser (except IE) work fine. IE doesn't like you to access something outside of localhost. So that was step 1 (beginner mistake)

But now that I've got everything up and running again, there is just one call , failing, only on IE : deleting a user.

sdk.sendRequest('users/delete.json', 'DELETE',null, callback,true);
 
or (non ssl)
 
 sdk.sendRequest('users/delete.json', 'DELETE',null, callback);

I get a response but it simply says 'Invalid argument'. For this call I need to be logged in. Logging in goes fine.

Any idea where I should be looking?

We've found out that with Internet Explorer it's important not to mix normal web pages (HTTP) and request data from SSL connections. This won't work as it's limited by Internet Explorer's XDomainRequest which is used in the cocoafish JS SDK.

More information here: http://blogs.msdn.com/b/ieinternals/archive/2010/05/13/xdomainrequest-restrictions-limitations-and-workarounds.aspx

We also had a problem with a div element having the ID 'options' which somehow interfered with a javascript variable 'options' in Internet Explorer.