Edge Breaks On Long URLs on herokuapp.com

Issue #9147478 • Assigned to Nicolas A.

Details

Author
JP D.
Created
Sep 30, 2016
Privacy
This issue is public.
Reports
Reported by 9 people

Sign in to watch or report this issue.

Steps to reproduce

Attempt to visit this URL in Edge. Notice the browser does not navigate to this 4039 character URL.

Edge also breaks when using similar URLs with the anchor data attribute. Once the URL reaches a certain number of characters you get unexpected behavior.

Also see this GitHub issue for the web app this was discovered in.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Christian F.”

      Changed Assigned To to “Venkat K.”

      Changed Assigned To from “Venkat K.” to “Nicolas A.”

      Changed Title from “Edge Breaks On Long URLs” to “Edge Breaks On Long URLs on herokuapp.com”

    • Any notice or solution? Having the same problem with long urls.

    • Also same problem here… One thing is Internet explorer not behaving as it should, but I had hoped that edge would keep up. My issue is with an example url like this: flems web sandbox

    • Happens to me too.

    • Please note that this is not only on herokuapp.com… It is any url at all.

    • I don’t know if this is related, but when trying to launch Edge with a long URL, it gets significantly truncated. Here’s an example of the only way I know of to launch a long URL from code:

      C:\Windows\System32\cmd.exe /c explorer "microsoft-edge:https://xxxxxxxxxxxxxxxxxxxxxxxxx.com/xxxxxxx/xxxxxxxxxxxxxx?signature=%2fjPKZr4vybqFRCBGx6MARmCD9AwM7zE9N6IoY2CQcSmsvtD7WSsf%2f0eEzlyG6KZYqjuc%2fTnHnO2wz%2fbzwfHlYDAkkLdu2RXMy2W1Y24%2bnazTKtsbyxOUySu5jSDotAyvMhOeLi3n6j7vN23rJPXXXTUKdN75apw%2bXpplkP1UisU3DJ5vubV91gIxKwu6jpNg9n9DGvj6aomX1gchO4yAP3ASn%2bPe7mhpofxPiblI71K0vP%2bLAXE5URO6bqgX0%2b41"
      

      This URL gets cut off at 245 characters. So far I have not found a way to send a long URL to Edge.

    • Updating my previous comment, it turns out this problem is related to CMD and not Edge as running “start microsoft-edge:{url}” works for very long URLs. However, since Edge doesn’t provide a better way to launch URLs from the command line it’s still culpable here. But my comment probably doesn’t relate directly to this issue.

    • Wish I could edit, I forgot to mention that I was running “start microsoft-edge:{url}” in PowerShell (which works for longer URLs).

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

    Sign in