3 ms·
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/17.17134 Hmm... looks like i
by tracker1 7y ago
Mozilla/5.0 (Windows NT 10.0; Win64; x64)
AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/64.0.3282.140 Safari/537.36 Edge/17.17134
Hmm... looks like it's entirely practical to look at the Chrome/version for feature detection. And that they are specifically adding Edge/* detection to disable Edge instead of detecting as chrome compatible.
Edit, sorry, wrong/old edge above.. new Edge below.
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.173.0
And the new "Edg" instead of "Edge" means they likely had to ADD detection to disable it.
- jchw 7y agoYeah, Edge/* is going to detect separately from Chrome. The issue is, prior non-Chromium based versions of Edge would also have a user agent that looks like Chrome as well, so those older versions will need to be treated differently. :( It's the same reason why everything still has Mozilla/5.0. To be completely clear, I am suggesting this is a bug. It even looks like a bug, since it ironically tells you to upgrade to "...Edge" while saying Edge is unsupported.
- AaronFriel 7y agoThis bug is specifically detecting the new version of Edge (which uses "Edg/") and allows users with other strings "E/", "Ed/", and even Spartan based "Edge/". Someone intentionally added code to single out Chromium based Edge.