Network Error 0x2ee4 on IE 11 XMLHttpRequest Post Aborted in some scenarios and GWT Status Code Exception 0 in some

By design Issue #10882817


Kevin A.
Feb 9, 2017
This issue is public.
Found in
  • Internet Explorer
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

We are using GWT 2.5.1 and Errai 3.0.4.Final

The error occurs when randomly when using normally but it occurs quite often also just leaving it idle. It happens on Windows 11 and 8 and doesn’t occur on Firefox

Ive replicated it more often than not on my machine of the following scenario
IE 11 with the following:
Version: 11.0.9600.18537
Update versions: 11.0.38 (KB3203621)
Product ID: 00150-20000-00003-AA459

Windows 7 64bit

I’ve attached some of the times the error occured and the console logs of it

Is there a workaround to this? and also this might be similar to


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Brad E.”

  • Any updates or anything i can do to help?

  • Microsoft Edge Team

    Changed Assigned To from “Brad E.” to “Steven K.”

  • Hello Kevin,

    Thank you for taking the time to use our site.

    This site is primarily for any feedback related to the MS Edge browser.  We are making only security related changes to IE. 

    If would be helpful us if you could reproduce this issue in a current release of the Edge browser.

    Thanks again for the support,

    The MS Edge Team

  • Hi I’ve attached the logs from Microsoft Edge retest. Thanks for your help

  • Hi Kevin,

    Thank you for sending the logs.  They are very useful.  I see an issue that will cause this behavior.  I am not saying this is the only issue.

    First log entry that caught my eye:

    HTML1114: Codepage iso-8859-1 from (HTTP header) overrides conflicting codepage utf-8 from (META tag)

    And then later in the same log file “console1.txt” line 238:

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

    This stackoverflow post appears to tie the issues all together.

    If interested in more details, here is a link with a lot of information.  Search for "Embedded encoding disagrees":

    The fix is to make sure the file’s actual encoding and the server’s/webpage’s meta charset match, otherwise the common iso-8859-1 to utf-8 character mapping failures will occur.

    Example for utf-8:

    <meta charset="utf-8">

    I hope this helps,

    The MS Edge Team

  • Thanks for the help, ill check it out.
    Can i get some opinion regarding the status code 0 errors?

  • I will take a look at status code 0 error and the link again in more detail.

  • Hi Kevin,

    I looked at the GWT and status code 0 link you sent.  That is a different issue regarding the handling of keep-alives.

    Either way, all of these issues, except one or two side cases I saw in all the reading appear to be working as expected.  Servers need to prune sessions and these time-outs are used to help recover resources.  This is a common problem with routers, server, etc. having lower settings than expected or really a complete mismatch with the expected use cases.  This is why Yura’s solution resolved what he was seeing by sending pings every 5 seconds:

    Same idea for Lance Clark’s suggestion to tune the keep alive time-out higher than the delay between XHR requests:

    This is an important part of a system engineer’s job, I.e. to plan the end to end system behavior and resources.

    Hope this helps,

    The MS Edge Team

  • Microsoft Edge Team

    Changed Status to “By design”

  • Hi for the
    HTML1114: Codepage iso-8859-1 from (HTTP header) overrides conflicting codepage utf-8 from (META tag)

    This error will appear and produce the 2ee4 error because of the utf-8 contents cant be converted to 8859-1 is this correct?

You need to sign in to your Microsoft account to add a comment.

Sign in