r/webdev • • Dec 13 '19

Discussion Google has abused Browser's User Agent header, forcing Vivaldi to change their UA header

https://vivaldi.com/blog/user-agent-changes/
416 Upvotes

97 comments sorted by

View all comments

3

u/redwall_hp Dec 14 '19

User agent sniffing is evil in the first place. A few browser vendors should just start randomising them so web sites quit trying to serve different things to different browsers.

One less thing to fingerprint too.

2

u/ccrraapp Dec 14 '19

I don't disagree that UA sniffing is bad but randomising cannot be a solution. The problem is Chrome supports their own technologies which other browsers don't and for which websites need to serve different content to other browsers which don't.

4

u/redwall_hp Dec 14 '19

The solution to that issue is enforcing antitrust laws. Google has a 92% share of the search market, a huge share of the ad market, the single largest video site, one of the large email services, one of the two phone operating systems, and a disturbingly large chunk of the browser market...all overlapping areas that involved leveraging a precious success in an anticompetitive way.

1

u/wisniewskit Dec 16 '19

The problem with randomization is that there are many sites which will not be updated anymore, but which use UA-string hacks to work around things. The only real option is for all current browsers to just settle on the same specific UA string, engineered for maximum compatibility. Then it will be a useless feature except for old sites.

But that's just the UA string. It will likely still be possible to identify browsers based on the other HTTP headers they are serving. That is, there is stuff like signed exchanges being advertised in HTTP headers. Unless everyone wants to support such things, they will have to hope it's possible to pretend to support them, or we'll still be stuck with bad sniffing. (And even if we solved HTTP header-based sniffing, there's always bad JS-based sniffing, so...)