The following piece of logic used to work with both jquery 1.4.4 and 1.7.1 on all mobile devices that we're supporting:

$.ajax({
  url: '',
  type: 'GET',
  dataType: 'text',
  timeout: 60000,
  success: function(data) {
    alert(data);
  },
  error: function(jqXHR) {
    alert(jqXHR.state());
  }
});

But with iOS 5.0.1, the above enters the error function alerting rejected without any actual HTTP requests. It seems that exactly one AJAX request will work before I need to restart my iPhone. Is this a known jquery / iOS 5.0 problem? How can I debug it? Is there any workaround? I don't know where to start looking.

NOTE: I've noticed on the server side, that instead of GET requests, OPTIONS requests are issued. This seems to be a related issue:

/

The following piece of logic used to work with both jquery 1.4.4 and 1.7.1 on all mobile devices that we're supporting:

$.ajax({
  url: 'http://www.example./someurl',
  type: 'GET',
  dataType: 'text',
  timeout: 60000,
  success: function(data) {
    alert(data);
  },
  error: function(jqXHR) {
    alert(jqXHR.state());
  }
});

But with iOS 5.0.1, the above enters the error function alerting rejected without any actual HTTP requests. It seems that exactly one AJAX request will work before I need to restart my iPhone. Is this a known jquery / iOS 5.0 problem? How can I debug it? Is there any workaround? I don't know where to start looking.

NOTE: I've noticed on the server side, that instead of GET requests, OPTIONS requests are issued. This seems to be a related issue:

http://spin.atomicobject./2012/01/20/mobile-safari-on-ios-5-1-unexpectedly-making-cross-origin-resource-sharing-requests/

• javascript
• jquery
• iphone
• ajax
• ios5

• Have you looked at the traffic between the phone and the server using something like Charles? – tkone Commented Feb 9, 2012 at 12:27
• @tkone: Hmm, yes I could find some traffic being blocked by our web entry server. It seems that the iPhone issues an HTTP OPTIONS request, which we reject... But why...? – Lukas Eder Commented Feb 9, 2012 at 13:25
• that's very odd. Do you have a sample page I can point my phone at? I have an iOS4 device as well I want to see if it happens on as we are about redo our mobile site to rely extensively on ajax... – tkone Commented Feb 9, 2012 at 14:00
• @tkone: Unfortunately, no. I can't make this publicly available... :-/ But iOS4 is still fine – Lukas Eder Commented Feb 9, 2012 at 14:10
• @tkone: N.B. I'm starting to feel that iOS 5 doesn't send cookies with XMLHttpRequest :-/ – Lukas Eder Commented Feb 9, 2012 at 14:43

3 Answers 3

The link that I provided in the question is actually pointing to the solution. Some of my ajax requests are used to fetch URL's of PDFs which are streamed using

Content-Disposition: attachment; filename="somename.pdf"

Apparently, that causes major issues in iOS 5.0's Safari, breaking the XMLHttpRequest object (it is not related with jquery). Crazy. Here's the link again:

http://spin.atomicobject./2012/01/20/mobile-safari-on-ios-5-1-unexpectedly-making-cross-origin-resource-sharing-requests/

Thank you for the investigation. I am having the same problem. After receiving a file as 'attachment' Mobile Safari sends OPTIONS request when calling:

$.ajax('/url')

BUT, if I run the following code from the same file, it generates a valid GET request:

http = new XMLHttpRequest()     
http.open("GET", "/url")
http.send()

Why jQuery is not working but XMLHttpRequest works here?

The reason for the error is the same origin policy. It only allows you to do XMLHTTPRequests to your own domain. See if you can use JSON instead.

References and remended resources;
https://stackoverflow./a/1109261/896341
http://api.jquery./jQuery.getJSON/
http://www.w3/Security/wiki/Same_Origin_Policy
https://developer.mozilla/En/Same_origin_policy_for_JavaScript