13

This problem is driving me nuts. Our web app uses HTTP POST to login users and now IE 10 is aborting the connection and saying: 

SCRIPT7002: XMLHttpRequest: Network Error 0x2f7d, Could not complete the operation due to error 00002f7d.

Here are all the details I have

  • IE version 10.0.9.16618, update version 10.0.6. I've also reproduced this on IE version 10.0.9200.16635, update version 10.0.7.
  • The domain is using HTTPS. The problem doesn't occur on HTTP connections
  • I've read that for some reason IE needs to get a certificate before it can do an HTTP POST, so I have HTTP GETs running before my POST request, but now the GET is erroring out. See network flow screen shot. The GET is super simple, just a PING page that returns "I'm up."
  • Asyn is turned off $.ajax({type: 'POST',url: url,async: false...}); I've read in other posts that this matters.
  • The certificate is good, see screen shot.
  • The problem goes away if the site is added as a "trusted site" but that's not really the user experience we're shooting for.
  • This just started about a month ago. Did Microsoft push some new updates recently?
  • I've already read: http://social.msdn.microsoft.com/Forums/windowsapps/en-US/dd5d2762-7643-420e-880a-9bf75554e383/intermittent-xmlhttprequest-network-error-0x2f7d-could-not-complete-the-operation-due-to-error. It doesn't help.

Screen shots:

Network flow: enter image description here

Cert is good:

enter image description here

Any help is greatly appreciated. I've spent a lot of hours on this with no luck. As you would expect this works fine in Chrome and Firefox. If you need any more detail about what's happening please let me know.

Thanks,

etherton
  • 924
  • 2
  • 10
  • 21

4 Answers4

4

Certificate revocation checks may block the initial JSON POST, but allow subsequent requests after the GET callback

We recently determined that URLMon's code (Win8, Win7, and probably earlier) to ignore certificate revocation check failures is not applied for content uploads (e.g. HTTP POST). Hence, if a Certificate Revocation check fails, that is fatal to the upload (e.g. IE will show a Page Cannot Be Displayed error message; other clients would show a different error). However, this rarely matters in the real world because in most cases, the user first performs a download (HTTP GET) from the target HTTPS site, and as a result the server's certificate is cached with the "ignore revocation check failures" exemption for the lifetime of the process and thus a subsequent POST inherits that flag and succeeds. The upload fails if the very first request to the HTTPS site in the current process was for an upload (e.g. as in a cross-origin POST request).

Here is how it works:

A little background: When a web browser initiates a HTTPS handshake with a web server, the server immediately sends down a digital certificate. The hostname of the server is listed inside the digital certificate, and the browser compares it to the hostname it was attempting to reach. If these hostnames do not match, the browser raises an error.

The matching-hostnames requirement causes a problem if a single-IP is configured to host multiple sites (sometimes known as “virtual-hosting”). Ordinarily, a virtual-hosting server examines the HTTP Host request header to determine what HTTP content to return. However, in the HTTPS case, the server must provide a digital certificate before it receives the HTTP headers from the browser. SNI resolves this problem by listing the target server’s hostname in the SNI extension field of the initial client handshake with the secure server. A virtual-hosting server may examine the SNI extension to determine which digital certificate to send back to the client.

The GET may be victim of the operation aborted scenario:

The HTML file is being parsed, and encounters a script block. The script block contains inline script which creates a new element and attempts to add it to the BODY element before the closing BODY tag has been encountered by the parser.

<body>
  <div>
    <script>document.body.appendChild(newElem)</script>
  </div>
</body>

Note that if I removed the <div> element, then this problem would not occur because the script block's immediate parent would be BODY, and the script block's immediate parent is immune to this problem.

References

Community
  • 1
  • 1
Paul Sweatte
  • 24,148
  • 7
  • 127
  • 265
1

[SOLVED]

I only observed this error today. for me the Error code was different though.

SCRIPT7002: XMLHttpRequest: Network Error 0x2efd, Could not complete the operation due to error 00002efd.

I was occuring randomly and not all time. but what it noticed is, if it comes it comes for subsequent ajax calls.. so i put some delay of 5 seconds between the ajax calls and it resolved.

Also the CORS must be configured on your web server.

Amit Shah
  • 7,771
  • 5
  • 39
  • 55
0

I had the same exact issue and I just finally resolved it. For some reason I got the same error that you were receiving on IE when connecting to the API using OWIN middleware that was used to receive login credentials. It seemed to work fine while connecting to any other sort of API though. For some reason it didnt like cross domain request even though I had CORS enabled server side on the API.

Anyways I was able to resolve the issue using the xdomain library. Make sure you load this script before loading any other javascript.

First create a proxy.html page on the root of your API server and add this code. Replace placeholder URL.

<!DOCTYPE HTML>
<script src="//cdn.rawgit.com/jpillora/xdomain/0.7.3/dist/xdomain.min.js" master="http://insert_client_url_here.com"></script>

Now simply add this to your client replacing the placeholder URL pointing to the proxy.html page on your API server.

<script src="//cdn.rawgit.com/jpillora/xdomain/0.7.3/dist/xdomain.min.js" slave="http://Insert_Api_Url_Here.com/proxy.html"></script>
m0g
  • 969
  • 2
  • 15
  • 30
0

Adding a delay is not a proper solution. This can be because the IE will treat it as an network error when the empty body request is made. Try adding a empty class as the parameter in the server and IE should start working.

Anirudh Adiga
  • 1
  • 1