{"id":100215,"date":"2021-05-20T10:23:08","date_gmt":"2021-05-20T08:23:09","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/v-chrome-eksperimentiruyut-s-podderzhkoj-rss-chistkoj-user-agent-i-avtosmenoj-parolej"},"modified":"2021-05-20T10:23:08","modified_gmt":"2021-05-20T08:23:09","slug":"v-chrome-eksperimentiruyut-s-podderzhkoj-rss-chistkoj-user-agent-i-avtosmenoj-parolej","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/v-chrome-eksperimentiruyut-s-podderzhkoj-rss-chistkoj-user-agent-i-avtosmenoj-parolej","title":{"rendered":"Chrome is experimenting with RSS support, cleaning User-Agent strings, and automatic password changes.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Google has announced the addition of an experimental \"Follow\" feature in Chrome, implementing a built-in RSS client. Users will be able to subscribe to the RSS feeds of their favorite websites via the Follow button in the menu and track new posts in the Following section on the new tab page. Testing of this new feature will begin in the coming weeks and will be limited to certain Chrome users on Android in the United States who are using the experimental Canary branch.

\"Chrome<\/center> <\/p>\n

Google has also published a plan to trim down the User-Agent HTTP header content. The reformation of User-Agent support was initially planned a year ago but was postponed due to the COVID-19 pandemic. It is noted that Safari and Firefox have already removed OS version details from the User-Agent. <\/p>\n

Chrome 89 has enabled the User-Agent Client Hints mechanism by default, which is being developed as a replacement for User-Agent. Now, Google intends to start experiments to reduce User-Agent related functionality. User-Agent Client Hints allows selective delivery of data about specific browser and system parameters (version, platform, etc.) only after a request. proxy server<\/a>. Users, in turn, can determine what information can be provided to site owners. <\/p>\n

When using User-Agent Client Hints, the identifier is not sent by default without an explicit request; only basic parameters are provided by default, making passive identification difficult. For websites that need detailed browser data on the first request, extensions like \"Client Hints Reliability\" have been developed, which include the HTTP header Critical-CH sent by the server, indicating that the site needs to receive \"Client Hint\" parameters in a separate request to render content, and the ACCEPT_CH extension in HTTP\/2 and HTTP\/3, which transmits information about the \"Client Hint\" parameters to be obtained at the connection level. server<\/a>. <\/p>\n

Until the migration to the Client Hints mechanism is complete, Google does not intend to change the behavior of the User-Agent in stable releases. At least in 2021, no changes will be made to the User-Agent. However, in the experimental branches of Chrome, experiments will begin with reducing information in the User-Agent header and the JavaScript parameters navigator.userAgent, navigator.appVersion, and navigator.platform. After this cleaning, it will still be possible to determine the browser name, significant browser version, platform, and device type (mobile phone, PC, tablet) from the User-Agent string. To obtain additional data, the User Agent Client Hints API will need to be used. <\/p>\n

Seven stages of gradual reduction of the User-Agent have been defined: <\/p>\n