IE Mode incorrect User Agent string on initial request to site beginning with Version 96.0.1054.29

%3CLINGO-SUB%20id%3D%22lingo-sub-3018662%22%20slang%3D%22en-US%22%3EIE%20Mode%20incorrect%20User%20Agent%20string%20on%20initial%20request%20to%20site%20beginning%20with%20Version%2096.0.1054.29%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3018662%22%20slang%3D%22en-US%22%3E%3CP%3EFirst%20of%20all%2C%20let%20me%20apologize%20for%20reporting%20a%20defect%20in%20this%20manner.%26nbsp%3B%20My%20organization%20has%20disabled%20most%20of%20Edge's%20communications%20with%20the%20outside%20world%2C%20including%20pressing%26nbsp%3B%3CSTRONG%3EAlt%2BShift%2BI%3C%2FSTRONG%3E%20to%20report%20this.%26nbsp%3B%20So%20I'm%20starting%20a%20discussion%20here%20in%20the%20hope%20this%20bug%20can%20get%20traction%20and%20be%20fixed%20because%20it's%20causing%20problems.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20Edge%20is%20running%20in%20IE%20Compatibility%20mode%2C%20it%20incorrectly%20reports%20the%20User%20Agent%20on%20the%20first%20call%20to%20the%20web%20server.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20reproduced%20this%20by%20writing%20a%20simple%20%22useragent.asp%22%20page%20(yes%2C%20our%20application%20still%20uses%20Classic%20ASP).%26nbsp%3B%20The%20UserAgent.asp%20basically%20consists%20of%26nbsp%3Bresponse.write(Request.ServerVariables(%22HTTP_USER_AGENT%22)).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20v95%20of%20Edge%2C%20if%20I%20call%20UserAgent.asp%2C%20I%20get%20this%3A%20%5BMozilla%2F5.0%20(Windows%20NT%2010.0%3B%20WOW64%3B%20Trident%2F7.0%3B%20rv%3A11.0)%20like%20Gecko%5D.%26nbsp%3B%20This%20is%20what%20the%20website%20was%20expecting.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20v96%20of%20Edge%20(from%20version%20v96.0.1054%20to%20the%20latest%20v96.0.1054.34)%2C%20if%20I%20call%20UserAgent.asp%2C%20I%20get%20this%3A%26nbsp%3B%5BMozilla%2F5.0%20(Windows%20NT%2010.0%3B%20Win64%3B%20x64)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F96.0.4664.55%20Safari%2F537.36%20Edg%2F96.0.1054.34%5D.%26nbsp%3B%20This%20is%20not%20expected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20interesting%20part%20of%20this%20bug%20is%20if%20you%20refresh%20the%20page%2C%20UserAgent.asp%20then%20returns%20the%20proper%20value!%26nbsp%3B%20Unfortunately%20my%20application%20behaves%20in%20such%20a%20way%20that%20refreshing%20will%20not%20fix%20the%20problem%20this%20causes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3018662%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EEdge%20v96%20defect%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

First of all, let me apologize for reporting a defect in this manner.  My organization has disabled most of Edge's communications with the outside world, including pressing Alt+Shift+I to report this.  So I'm starting a discussion here in the hope this bug can get traction and be fixed because it's causing problems.

 

When Edge is running in IE Compatibility mode, it incorrectly reports the User Agent on the first call to the web server.  

 

I've reproduced this by writing a simple "useragent.asp" page (yes, our application still uses Classic ASP).  The UserAgent.asp basically consists of response.write(Request.ServerVariables("HTTP_USER_AGENT")).

 

In v95 of Edge, if I call UserAgent.asp, I get this: [Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko].  This is what the website was expecting.

 

In v96 of Edge (from version v96.0.1054 to the latest v96.0.1054.34), if I call UserAgent.asp, I get this: [Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36 Edg/96.0.1054.34].  This is not expected.

 

The interesting part of this bug is if you refresh the page, UserAgent.asp then returns the proper value!  Unfortunately my application behaves in such a way that refreshing will not fix the problem this causes.

2 Replies

@Craig_Chatterton 

Hi Craig,

we had the same problem. It occurred with v96 of Edge and installation of KB5007186. Can be fixed with a registry entry:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge]
"InternetExplorerIntegrationComplexNavDataTypes"=dword:00000001

https://docs.microsoft.com/de-de/deployedge/microsoft-edge-policies#internetexplorerintegrationcompl...

It looks like Edge v96.0.1054.53 has finally resolved this issue. UserAgent is now being reported correctly.