The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
1–10 of 143 posts
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#2I get this warning for TSB in the UK. I was wondering why, despite having the latest version.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#3The more this happens the more Chrome deciding to freeze the UA string forever makes sense.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#4The more this happens the more Chrome deciding to freeze the UA string forever makes sense.
It's not a bad idea for security either, as a way to combat fingerprinting efforts.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#5[flagged]
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#6Are they talking about only MacBook Pros with Intel chips since they reference Butterfly keyboards or is that sarcasm that sort of feels out of place ?
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#7[flagged]
It's anything that communicates via HTTP. A WebDAV file manager isn't a web browser. It's still a user agent.
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#8The more this happens the more Chrome deciding to freeze the UA string forever makes sense.
Looks like that's been replace by "Reduce User-Agent request header
Reduce (formerly, "freeze") the amount of information available in the User-Agent request header. See https://www.chromium.org/updates/ua-reduction for more info. – Mac, Windows, Linux, ChromeOS, Android, Fuchsia, Lacros
#reduce-user-agent"
Re: The IE 11 user-agent forced Mozilla to freeze part of its user-agent string
#9In retrospect, wasn't putting "Mozilla" in your user-agent string when you aren't the Mozilla Foundation or project a trademark violation, that they could have enforced?