![]() Unification also allows you to get rid of obsolete and meaningless attributes such as 'Mozilla / 5.0', 'like Gecko' and 'like KHTML' in the User-Agent string.Īs a replacement to User-Agent, the User-Agent Client Hints mechanism is proposed, which implies the selective return of data on specific browser and system parameters (version, platform, etc.) only after a request by the server and giving users the ability to selectively provide similar information to site owners. At the same time, the fake User-Agent in second-tier browsers is also stimulated by Google itself, as User-Agent blocks the entrance to its services. In accordance with the current plan, access to the erAgent property will be declared obsolete in Chrome 81, scheduled for March 17, Chrome 83 will stop updating the browser version and unify operating system versions, and Chrome 85 will unify the line with the operating system identifier (it will only be possible to determine the desktop and mobile OS, and for mobile versions, information about the typical sizes of the device will probably be given).Īmong the main reasons for unifying the User-Agent header is its use for passive fingerprinting, as well as the practice of faking the header with less popular browsers to ensure the functioning of individual sites (for example, Vivaldi is forced to present itself to sites as Chrome). The initiative is already supported by the developers of Edge and Firefox, and is also already implemented in Safari. No plans to delete the User-Agent header yet. The developers of Chromium proposed to unify and freeze the contents of the User-Agent HTTP header in which the name and version of the browser are transmitted, as well as restrict access to the erAgent property in JavaScript. ![]() ![]() Chromium developers have proposed to unify and expire the User-Agent header ![]()
0 Comments
Leave a Reply. |