News for hackers. Stuff that matters.

A comment on Google Chrome's fear of Microsoft Edge is revealing its bad side. Parent comment

Re:Google Chrome's fear of Microsoft Edge is revealing its b... by sebazzz on Wednesday February 26, 2020 @10:46AM (#22423994)
The user agent is equal to Chrome with "Edg" (not a typo) appended:

> mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/76.0.3800.0 safari/537.36 edg/76.0.167.1

Certainly not an accident, unless they tried to save one byte by not checking on the full "Edge" token.

[ Parent | on HN ]
Re:Google Chrome's fear of Microsoft Edge is revealing its b... by jmcphers on Wednesday February 26, 2020 @02:42PM (#22426499)
They serve this UA on purpose to some sites to prevent being detected as the "old" Edge (which was not Chromium-based).
[ Parent | on HN ]
Re:Google Chrome's fear of Microsoft Edge is revealing its b... by lallysingh on Wednesday February 26, 2020 @11:00AM (#22424127)
Very well could be an internal project/component name in MS.
[ Parent | on HN ]
Re:Google Chrome's fear of Microsoft Edge is revealing its b... by cpeterso on Wednesday February 26, 2020 @11:31AM (#22424471)
Microsoft's purposely changed Chromium Edge's User-Agent string to say "Edg" [sic] instead of "Edge". They wanted to give sites a way to identify Chromium Edge without accidentally treating it was the old Trident Edge (whose User-Agent string says "Edge"). No one would have written User-Agent string sniffing code that searches for "Edg" instead of "Edge" before Chromium Edge was released.

Thus, Google sites are explicitly targeting Chromium Edge because the only way to differentiate Chrome from Chromium Edge is for the server is to search the User-Agent string for "Edg". If they just searched for "Chromium", then Chromium Edge would be successfully match.

[ Parent | on HN ]