Edge does not redirect to URL containing a query string on XHR

Fixed, not yet flighted Issue #9200705

Details

Created
Oct 5, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
14.14393
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

After installing Window Update KB3194496, Edge does not redirect to URL containing a query string on XHR.

    var xhr = new XMLHttpRequest();
    xhr.open('GET', '/endpoint', true);
    xhr.send(null);

If /endpoint returns status code 302 and Location header Location: /endpoint2?a=1 , Edge does not redirect and shows the following error message.

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

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

    • I found that this issue occurs only when ExtJS library was loaded. ExtJS 4.x does not support Microsoft Edge?

        
      
    • This issue can be reproduced with latest ExtJS release.

      https://cdnjs.cloudflare.com/ajax/libs/extjs/6.2.0/ext-all-debug.js

    • I found a minimal reproducible code without ExtJS.

          (new DOMParser()).parseFromString('', "application/xml");
          var xhr = new XMLHttpRequest();
          xhr.open('GET', '/endpoint', true);
          xhr.send(null);
      

      If /endpoint returns status code 302 with Location header Location: /endpoint2?a=1 , Edge does not redirect and shows the following error message.

      SCRIPT7002: XMLHttpRequest: Network Error 0x800c0008, The download of the specified resource has failed.
      
    • Tags in code block look like not escaped, even though preview looks good.
      I wrote the following code.

      (new DOMParser()).parseFromString('<a/>’, “application/xml”);

    • KB3197356 (released today) seems to resolve this issue.

    • Thank you for your feedback and the updates. Could you please confirm the issue no longer repro so we can close this feedback item.

      Best regards,
      The MS Edge Team.

    • I confirmed the issue was resolved. Is there any detailed information about this issue?

    • Microsoft Edge Team

      Changed Status to “Fixed”

    • No that will be enough, and we will close this bug as fixed for now. Please feel free to reactivate the bug if see any inconsistency regarding to this issue. Thanks again for your assistance in the investigation. We continue to welcome more feedback and look forward to hearing from you again soon.

      All the best,
      The MS Edge Team

    • Microsoft Edge Team

      Changed Steps to Reproduce

    • Additional information about the issue addressed by KB3197356 is at https://support.microsoft.com/en-us/kb/3197356.

      We’d like to confirm that what you ran into is the same issue that we addressed.
      Can you confirm that the source page issuing this XHR has a charset value defined, such as "euc-jp"? It would be set by the HTTP response header Content-Type, an equivalent meta http-equiv tag, or a meta charset tag in the page. If you have an URL demonstrating the issue that would also be useful for us to confirm that what you are reporting is the same issue.

    • Microsoft Edge Team

      Changed Assigned To to “Erik A.”

    • I’m not sure that our problem is the same as the issue addressed by KB3197356. The source page has a Content-Type header 'Content-Type:text/html; charset=UTF-8’. Could you check my demo page?

      http://yehara-redirect-test1.herokuapp.com/index.html

      Press the ‘test’ button to reproduce the error. The error will occur only if KB3194496 is installed and KB3197356 is not installed.

    • Microsoft Edge Team

      Changed Status from “Fixed”

      Changed Status to “Fixed, not yet flighted”

    • Thank you for the additional repro. The underlying issue was a little bit broader than initially thought. It has now been fully addressed and your demo page continues to work. Thanks for taking the time to report this issue!

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

    Sign in