XMLHttpRequest incorrectly reports status 0

Issue #14407632 • Assigned to James M.

Details

Author
André R.
Created
Oct 27, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
40.15063
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

On my page, I’m calling a web service using JQuery’s post method. This works in Chrome, Firefox and the latest Internet Explorer. However, in Edge, that exact same call reports status 0 (instead of 400, which would be correct), and fails. After some tests, I finally came to the conclusion that the error must lay somewhere in Edge itself, because it can be reproduced with a pure XMLHttpRequest.

Please visit this jQuery ticket for additional information and sample code.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “James M.”

    • Hello,

      Thank you for providing this information about the issue. Unfortunately, we are unable to reproduce this problem in Edge with the information at hand. Please update this case when you can provide us with the API address or a full working sample to test.

      Best Wishes,
      The MS Edge Team

    • I experience the same behavior when I try to connect to a server on my local network.
      Edge doesn’t send the request and returns error 0. All other browsers, including IE11, send out the request and return the correct server response.

      The server on the local network is just a local copy of the remote server on the internet, but because Edge doesn’t even send the request, a server difference can’t be the issue. The only change I made to the request to make it work in Edge is the hostname, which I changed to a hostname that that points to an external IP (listed in DNS records). The server on the local network has its hostname listed in my hosts file.

    • Hello Erik,

      I was actually taken in by the fallacy, that I tested both sites locally. However, the "old version", where it worked, ran on one of our internal servers. After publishing my updated code to that server, it magically worked again.

      So the actual problem of this bug is, that XHR requests seem to don’t work when connecting to a server via localhost. Additionally, the error message is misleading, because it doesn’t state at all, why this happens. However, I think, if the first bug will get fixed, the second “imperfection” becomes irrelevant anyways.

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

    Sign in