Skip to main content

Bug Tracker

Side navigation

#3436 closed bug (invalid)

Opened October 01, 2008 02:06PM UTC

Closed March 18, 2009 10:53PM UTC

Last modified March 14, 2012 05:51PM UTC

IE6 freezes when receiving certain JSONP AJAX responses

Reported by: anschoewe Owned by:
Priority: major Milestone: 1.3
Component: ajax Version: 1.2.6
Keywords: Cc:
Blocked by: Blocking:

I've encountered a problem when retrieving a JSONP response from a server in a different domain using IE6.

When I make the same AJAX call using JSONP to a server in the same domain as the web page, all goes well in all browsers (including IE6). However, when I make calls between domains (XSS) using JSONP, Internet Explorer 6 locks up. Specifically, the CPU spikes to 100% and the 'success' callback is never reached. The only time I have had success going between domains is when the response is very short (less than 150 bytes typically). The length of the response seems important.

I'm using jQuery 1.2.6. I've tried the $.getJSON() method and the $.ajax(dataType: "jsonp") method without success. This works beautifully in FF3 and IE7. I haven't been able to find anyone else with a similar problem. I thought this type of functionality was fully supported by jQuery in IE6.

Attached is the code for the HTML page making the AJAX call. Make a local copy of this file (and jquery library) and give it a shot using IE6. For me, it always causes the CPU to spike with no response rendered.

Attachments (1)
  • TestResults.html (1.1 KB) - added by anschoewe October 01, 2008 02:09PM UTC.

    An example file for use for testing. Make a local copy and try it.

Change History (4)

Changed October 01, 2008 02:27PM UTC by flesler comment:1

component: unfilledajax
owner: flesler

Changed March 18, 2009 10:23PM UTC by brandon comment:2

resolution: → duplicate
status: newclosed

Consolidating this into #4378

Changed March 18, 2009 10:52PM UTC by brandon comment:3

resolution: duplicate
status: closedreopened

Changed March 18, 2009 10:53PM UTC by brandon comment:4

resolution: → invalid
status: reopenedclosed

This is because the response from the server doesn't seem to be valid. See also this same issue asked on Stackoverflow: