CORS Issue iframe

Confirmed Issue #11451575 • Assigned to Nicolas A.

Details

Author
Venkatakrishnan K.
Created
Mar 30, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

In our website, we try to access a url [ajax] of another domain from within an iFrame. OPTIONS is being sent to verify whether to allow or not.

Randomly these OPTIONS call take huge time to get the response and some comes in milliseconds. This work fine in all modern browsers even in IE 11 but not in EDGE.

Attached some screenshots which explains the behaviour.

Attachments

1 attachment

Comments and activity

  • Its kinda urgent for our company as we have public release next week, where edge users are facing problem. It would be great if some technical person look at this sooner.

  • Hi Venkatakrishnan,

    I will look at it today and let you know.

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

  • Ventaktakrishnan,

    Can you send your ajax code for the request you believe is causing the issue?

    Also, can you provide the Windows/Edge version you are using? (Go to start menu, type “winver” in
    search box and then press Enter)

    Thank you

  • Microsoft Edge Team

    Changed Assigned To to “Lee H.”

  • Steven K,

    Thanks for the response.

    1. The issue was noticed in the windows 10 systems, where automatic updates are enabled and having latest versions.
    2. Important Note: This started happening very recently, as couple of weeks back we did not notice any issue in the EDGE. Any recent updates ?
    3. As an immediate fix we made some code changes to avoid any CORS and no issues now noticed in EDGE, as we are nearing a public release. But this resulted in our proposed architecture to be changed.
    4. Attached a javascript which explains how we do a AJAX call.
  • Microsoft Edge Team

    Changed Assigned To to “Venkat K.”

    Changed Assigned To from “Venkat K.” to “Scott W.”

    Changed Status to “Confirmed”

  • I see the status as confirmed.
    Request you to share the status and workaround if any till the issue is solved

  • Microsoft Edge Team

    Changed Assigned To from “Scott W.” to “Nicolas A.”

    Changed Title from “CORS Issue iframe” to “CORS Issue iframe”

  • Hello Venkatakrishnan,

    I’ve been looking into this issue today and I’ve been having a bit of trouble reproducing the bug. I think I’ll need some more information in order to set up a good repro it that’s alright:

    1. What is the specific version of Edge you are using? You can check in “Settings” in menu from the “…” button in the top right. For example:
    1. What is the specific version of the OS in which you are seeing the issue? As Steven mentioned, you can find this by going to the search box (windows key), typing "winver", and hitting Enter. For example:

    3
    . Could you provide a test page which reproduces the issue using the Ajax code you’ve provided? I’ve created a test page based on the description of the issue so far, but I might be missing something.

    4
    . If possible, could you provide some Fiddler (http://www.telerik.com/fiddler) traces I can examine? Please note that this is NOT a good option if the requests in the trace contain sensitive data.

    This will help me debug the issue and get it fixed (if it hasn’t been fixed already) :)

    Thanks,

    Nicolas

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

Sign in