HTTP Post of form data adds random characters

Fixed Issue #17477791


Sabahattin K.
May 11, 2018
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 13 people

Sign in to watch or report this issue.

Steps to reproduce

whenever i tried to update my database with edge browser only it adds random characters to the value selected


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • Hi Sabahattin,

      Will you provide a repro for this?  I need to be able to be able to reproduce this issue.

      Thank you for the help,


    • I’m having the same problem. We have a classic ASP application which POSTs values from a select tag back to the server. Edge (42.17134.1.0) will add a random character to the end of the selected value when the POST occurs about 90% of the time. I know that it’s being generated by Edge because I can see it in the POST values in Fiddler. I’ve tested it in IE, Chrome, and Firefox, and the behavior does not occur in any other browser. I also tested an earlier build of Edge (38.14393.2068.0), and it does not occur there, either.
      To further complicate matters, it only occurs on the first 2 columns of 15 total columns in the form table.

    • Also see Issue #17358578, at it appears to be the same problem.

    • Microsoft Edge Team

      Changed Assigned To to “Mohamed S.”

    • This is bad TBH… Repros for me.

    • You can reproduce this problem on our shopping basket page as you go through the checkout process. The page is returned with errors as there are bad characters appending to the data in several of the credit card fields.

      It is specific to every user that attempts to checkout with Windows 10 Edge 17.17134.

      This problem began with the release of this version and is increasing in frequency as more browsers get updated.

      Contact me at and I can show you the issue. This is a major problem. Is there a workaround as of yet?

      field user entered value Error

      card_exp_month 11@
      card_exp_year 2019댊

    • We competed a workaround today, but seriously Microsoft, this is a bad bug in your browser.

    • We have the same issue. We have notified all our customers to not use Edge until this issue is resolved.

    • I reproduced and worked on some solutions.

    • Any eta on a bug fix?
      We have implemented workarounds and are telling users to avoid Edge.

      I do not understand how Microsoft has known about such a terrible bug since early May and has still not released a fix.

    • They should release an emergency fix. Pretty astounding this made it past QA, and has not been fixed for weeks.

    • Hello all,

      I was able to create a repro for this and forwarded that on about 4 days ago.  I believe you can see the update when the ticket was assigned to no one and then again to someone in the correct team (part of the process).  The issue is being worked on.  I apologize for not sending an update.  I do not have information on when the fix will be available yet.  We will post back when we do know more.

      @Steve K., excellent repro.  Appreciate you creating that.  I did not try the injectable and also did not create a repro with all the options at once, so that is very nice.


    • Microsoft Edge Team

      Changed Title from “html select tag adds random characters” to “HTTP Post of form data adds random characters”

    • @Alex, what was your workaround?

      It appears based on Steve K’s (not me) repro that explicitly setting the option values will prevent this issue from happening.

      <select name="edge2">
                  <option value="N">N</option>
                  <option value="Y">Y</option>

    • Any new info on the release date of the Edge update that corrects this issue?

    • How long will it take to fix Edge to support this very long standing SELECT element? Do we tell all users of Edge to stop using it even though it’s likely only a subset of Edge browser users (those on the latest version)? It would seem a fix is better than every web site containing warnings not to use Microsoft Edge browsers and choose competitors instead.

    • I’m telling everyone to permanently stop using Edge browser. The fact this bug with a Select statement passed QA and is not fixed a month later, tells me this browser is not a good choice.

    • A July Windows update for Windows 10 1803 fixed this error for us.

    • Hi Christopher,

      Thank you for the update.  Will you provide the extended version of Windows 10 you are using?  Win + S and type “winver” and hit enter.  This is so that others that find this site will know the version this fix was made publicly available in a non-insider release.

      Appreciate the support,

      The MS Edge Team

    • @Chrisopher R, What version of Edge does it show now? We also did a July update for Windows 10 a day or so ago, and we noted no change to the Edge version 17.17134 which is what we’re currently blocking users of.

    • My version shows: Microsoft Edge 42.17134.1.0, Microsoft EdgeHTML 17.17134

    • Same, so how could it be fixed if the version number did not change?

    • I can only tell you that I no longer get extra characters when I use the test URL at that I gave to Microsoft at the beginning of this. I have a .1.0 on the first version above, maybe that reflects the updated Edge app?

    • I also tested with two devices on Tuesday at 1:00pm when the updates came out. I had the problem with the test URL above on a non-patched device, and did not on a patched device minutes later.

    • Ok, thanks for the info!

    • Microsoft Edge Team

      Changed Status to “Fixed”

    • This fix is in the July RS4 Windows 10 update, thanks for the feedback!
      You can check if you have the fix by looking in settings -> System -> about shows the 
      OS Build == 17134.165 or higher
      Hope this helps!

    • That’s great, but it would be nice if the 17.17134 had changed as it’s what we test for in the user agent to block users. Now it will block users with bad versions as well as those patched. So Edge users will continue to be pestered for having a broken version until that changes in the user agent.

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

    Sign in