Google takes first step in freezing user agent strings (UAs) in Chrome

Google, which plans to deprete and freeze user agent strings in Chrome on desktop sm, and mobile devices, has added a “Freeze User-Agent request header” tag to its browser settings page to freeze the Canary version of the UA request header. If this tag is enabled, Chrome will now display the version number of the user agent string as 75 instead of 81 on the Chrome, on Windows and Android, and the third-party tool will also detect that this version of Chrome version number 75.

Google takes first step in freezing user agent strings (UAs) in ChromeGoogle takes first step in freezing user agent strings (UAs) in Chrome

Here’s some context for Google’s actions on its UA string. If you now access the chrome,” the chrome,”verison page, it will display information about the browser, such as user agent strings, profile paths, and executable paths. Whenever you visit a website, the site detects the browser you’re using by detecting UA and provides different content based on that tag, which is often used by website developers to deny access to websites in certain browsers.

When visiting certain Google services and other specific websites, the most affected Vivaldi and Firefox browsers and their users will be asked to use Chrome. That’s why Vivaldi let go and remove its name, Vivaldi, from its UA string to show Chrome’s UA string instead.

From a privacy perspective, the Chrome development team believes that UA has been used as a tool for fingerprinting users, which is why it wants to “freeze and unify (but not remove the User-Agent string in http requests as well as” navigator.” UserAgent in the UserAgent) UA string.

To address this issue, the company has developed the following schedule:

Google takes first step in freezing user agent strings (UAs) in Chrome

It’s a long process, and other browser vendors are involved. So far, the Chromium team has only added a mark to take the first step.