- You browse to a certain webpage by using Internet Explorer 10.
- The webpage contains a script that makes an asynchronous XMLHttpRequest (XHR) request when the webpage is opened.
- You close the webpage during the XHR request.
- The response for the XHR request is larger than 2 KB (including the header data).
Note This issue occurs in Internet Explorer 7, Internet Explorer 8 and Internet Explorer 9 document modes in Internet Explorer 10.
Security update informationTo resolve this issue in Internet Explorer 9 or Internet Explorer 10, install the most recent cumulative security update for Internet Explorer. To do this, go to the following Microsoft website:
- This update for Internet Explorer 10 was first included in the following security update:2838727 MS13-047: Cumulative Security Update for Internet Explorer: June 11, 2013
- To install this update for Internet Explorer 9, click the following article number to view the article in the Microsoft Knowledge Base:
2905733 Internet Explorer loses HTTP connections when you close a webpage before you receive an XHR response
- For more technical information about the most recent cumulative security update for Internet Explorer, go to the following Microsoft websites:
- Change the XHR request to a synchronous request.
Note This workaround is against best programming practices and may cause the web browser to freeze if there is no response. For more information, see Why You Should Use XMLHttpRequest Asynchronously.
To avoid a Windows Internet (WinINet) connection leak together with AJAX, you can end the existing connection before the window closes.
Note For more information about how to work around the connection leak, click the following article number to view the article in the Microsoft Knowledge Base:886710 Internet Explorer appears to stop responding, and you may also notice a memory leak on the computer
- Replace the window.open method with the window.showModalDialog method.
Note this workaround prevents user interaction with the parent window until the child window is closed.
- End existing asynchronous XHR requests from the OnUnLoad event. For example:
if (g_xmlHttpRequest != null && g_xmlHttpRequest.readyState != 4)
- Do not make asynchronous XHR calls from the OnUnLoad event.
Note Even if you make the calls from the OnLoad event this issue may still occur.
- Upgrade to Internet Explorer 10 and make sure that you use the native XHR implementation.
- Increase the maximum number of connections.
Article ID: 2856746 - Last Review: Nov 20, 2013 - Revision: 1