EDGE address bar limited to 2084(3)chars , causes oauth implicit flow to fail.

Issue #17367725 • Assigned to Venkat K.

Details

Author
Sondre N.
Created
May 3, 2018
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
42
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

We have to warn our users from using edge because it won’t allow all the parameters to be passed in the navigation bar on redirect from our IDserver. the full uri with parameters ends up at about 2800-3100 chars, dependent on claims. This gets truncated to 2083 chars, and is no longer a valid response.

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

  • Hi Sondre,

    I tested sending over 20,000 characters and was able to see the log on the server showing the parameters were all sent.  I also received my response message.

    Perhaps the IDserver is limiting the size?

    Can you provide a repro for this so we can review and test it?

    Will you also provide the extended version of Windows 10 you are using?  Win + S and type “winver” and hit enter.

    I have attached the test repro that I used.  Here are the instructions to use my repro:

    Repro Steps:

    • NOTE: Requires node.js to but installed
    • Unzip the zip file
    • open a shell in this folder.  I used git bash
    • cd public-repro/serverA
    • npm update
    • node index.js
    • Open browser
    • Open the debugger/F-12 and click on the network tab
    • Navigate to the URL:
           http://127.0.0.1:3000/
    • click the “Send Request” button
    • The request size will be display in the node.js console, E.g. the git bash shell
    • You will also see the request and response in the debugger.

    Appreciate the support,

    Steve

  • Microsoft Edge Team

    Changed Assigned To to “edgedevtoolstri”

  • I did a little modification, as the problem happens when redirectiong the window. Url fetching works just fine. If you run this, the URL gets shortened to 4074, wich I guess I read somewhere is the limit. Chrome, ff and safari doesn’t cap the url. I’m guessing that redirecting across domains is what causes the additional shortening to 2083.

  • the windows.location.href.length is 4096, but if you select all and try to count it is 2083

  • Thank you for the update.  I will try with a redirected URL.

  • Microsoft Edge Team

    Changed Assigned To to “Arvind M.”

    Changed Assigned To from “Arvind M.” to “Venkat K.”

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

Sign in