Forum Discussion
Wrong user agent?
athosbr99 it's a delibreate change, check https://blogs.windows.com/msedgedev/2019/04/08/microsoft-edge-preview-channel-details/ ; there is a paragraph titled "User Agent String" that explain why it had to be made 😊
Here it is :
User Agent String
With Microsoft Edge adopting Chromium, we are changing our user agent string to closely resemble that of the Chromium user agent string with the addition of the “Edg” token. If you’re blocking site access on user agent strings, please update your logic to treat this string as another Chromium-based browser.
Below is the user agent string for the latest Dev Channel build of Microsoft Edge:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.48 Safari/537.36 Edg/74.1.96.24
We’ve selected the “Edg” token to avoid compatibility issues that may be caused by using the string “Edge,” which is used by the current version of Microsoft Edge based on EdgeHTML. The “Edg” token is also consistent with https://blogs.windows.com/msedgedev/2017/10/05/microsoft-edge-ios-android-developer/ used on iOS and Android. We recommend that developers use feature detection where possible and avoid browser version detection through the user agent string, as it results in more maintenance and fragile code.
AimanJ awkward but I imagined something like that. but most services detect it as Chrome anyway. thanks for the link and info :)
athosbr99 It's a pleasure, & you are right about how some services detect it: in a way, it serve the point, since it's based on chromium (and thereof share the same features), & some sites/webapps rely on user agent to check compatibility, it basically tell them to treat it as if it's Chrome.
Again, glad to be of help, & have a nice day 🙂