3 ms·
From Google: “The browser must identify itself clearly in the User-Agent. The browser must not try to impersonate another browser like Chrome or Firefox.” Whi
by varenc 6y ago
From Google:
“The browser must identify itself clearly in the User-Agent. The browser must not try to impersonate another browser like Chrome or Firefox.”
Which is a bit funny considering that Chrome impersonates Mozilla, Safari, and Gecko! (As do all browsers)
Chrome’s User-Agent for reference:
“Mozilla/5.0 (Macintosh; Intel Mac OS X 11_0_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.66 Safari/537.36”
Spoofing other browsers is a long standing tradition. Funny to see Google trying to forbid it. Here’s a great history on User-Agents: https://webaim.org/blog/user-agent-string-history/ https://webaim.org/blog/user-agent-string-history/
- brendoelfrendo 6y agoFurthermore, wasn't Google talking about phasing out and replacing user-agent strings? User-agent leaks data and is somewhat fingerprintable, so the idea was to further genericise Chrome UA strings and adopt a new standard for sharing data about the client. Found an article: https://www.zdnet.com/article/google-to-phase-out-user-agent-strings-in-chrome/ https://www.zdnet.com/article/google-to-phase-out-user-agent...
- Fnoord 6y agoUsing privacy.resistFingerprinting in Firefox on a Mac makes it appear like an other browser version of Firefox, on another OS (Windows).
- Aissen 6y agoAnd you forgot Konqueror with the KHTML engine.