IE10/11 Ajax XHR error - SCRIPT7002: XMLHttpRequest: Network Error 0x2ef3

Question

I\'ve been working on this problem for a few days and reaching out on this forum since I feel like I\'ve exhausted my options. I have a form hosted on a Drupal 7 website an

Answer 1

I was seeing this error randomly with IE 8+9+10+11 Ajax calls. All other browsers did not have the problem.

It suppose there was a race-condition between KeepAlive connections. I am using Apache 2.4.7.

With the Apache 2 default settings in /etc/apache2/apache2.conf I was able to reproduce the error about every tenth Ajax call:

KeepAlive On
KeepAliveTimeout 5

Solution: Either setting

KeepAlive off

or

KeepAliveTimeout 1

solved the problem for me. I recommend anyone experiencing the 0x2ef3-Network error to fist set KeepAlive off on the server. If the error is gone, switch it on again and test with the values of KeepAliveTimeout. They can also be set to ms.

There is also a way to disable KeepAlive only for Internet Explorer.

Answer 2

Just want to give my take on what was the root cause of this issue for me.

We have an Angular2 app, that is calling our NodeJS REST api. The rest API then calls another service (SOAP I believe).

We found out that our SOAP service did not have the endpoint(?) in only one environment (worked everywhere else). When the NodeJS api was calling the SOAP service, the soap service was returning an error saying 'X is not a function'. When the error response was returned to NodeJS, it did not have the proper error/exception handling, so it was completely killing the service. Thus, the UI was not getting a response.

Answer 3

In my environment, I first copied/pasted some old codes to take use of. So the "contentType" was "application/json".

When I found out IE11 over windows 8 does NOT work in a very high probability, as long as I clicked submit button using my mouse. But I also found out the if I pressed the enter key in my keyboard, then it works just fine with IE11.

Note that my input elemnts and submit button were nested in a form element.

After struggling for a while, I came to this page, but didn't solve my problem, because I knew nothing about backend technologies. I was just a front-end guy with limited knowledge.

Then I tried a lot of modifications one by one. Suddenly the jQuery official API documents inspired me. I commented out the "contentType" parameter so that the "contentType" takes the default value, which is "application/x-www-form-urlencoded; charset=UTF-8". Then problem is solved.

Hope this will help.

Answer 4

The OP provided a WireShark capture showing that the server requested a certificate using the HTTPS CertificateRequest message and the client then immediately FINd the connection.

After configuring the server not to request a client certificate, the problem went away.

Using Fiddler also would make the problem disappear because, unless you configure it to do so, Fiddler will never request a client certificate from the browser.

I'm wondering if only the affected client machine had a matching certificate and/or whether the withCredentials flag on the CORS XHR request is relevant in this scenario.

Answer 5

I had a similar situation and after much research, the issue was a different one, but I want to post it here in the hopes that someone might find it helpful looking for the same error:

Apache had a connection timeout of 5 seconds. Internet explorer 11 on Win 7 seemed to ignore the fact that there was no active session anymore, assuming it would be 60 seconds. After changing the Apache settings to a timeout of 60 seconds, my issue was resolved.

Answer 6

We were seeing the same error in IE11 and Edge. A jQuery AJAX request was throwing the error XMLHttpRequest: Network Error 0x2ef3, Could not complete the operation due to error 00002ef3. consistently after exactly 300s. (Chrome & Firefox were fine)

Turned out to be an idle timeout setting on our load balancer (F5 in our case). We managed to diagnose the issue using Fiddler, which resulted in a more helpful error message in the browser: Failed to load resource: the server responded with a status of 504 (Fiddler - Receive Failure) Note that with Fiddler running, we saw this error (after 300s) in all browsers, including Chrome and Firefox.