![]() The User Agent Client Hints (UA-CH) feature provides an alternate source for the information the User-Agent string provides, both in its request header form as well as its JS API one. ![]() There have been past attempts at UA string freezing from the Safari team, but without an alternative way to perform UA based content-negotiation, they had to be partially reverted. The above abuse makes it desirable to freeze the UA string and replace it with a better mechanism. On top of those privacy issues, User-Agent sniffing is an abundant source of compatibility issues, in particular for minority browsers, resulting in browsers lying about themselves ( generally or to specific sites ), and sites (including Google properties) being broken in some browsers for no good reason. It contains many details about the user’s browser and device as well as many lies ("Mozilla/5.0", anyone?) that were or are needed for compatibility purposes, as servers grew reliant on bad User Agent sniffing. The User-Agent string is an abundant source of passive fingerprinting information about our users. Contact, want to freeze and unify (but not remove ) the User Agent string in HTTP requests as well as in `erAgent`
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |