Browsers should probably just stop sending user-agent header at all, ideally.
If anyone else was wondering why some websites and the “Alternate Player for Twitch.tv” extension stopped working in the latest Librewolf update, it’s because they changed the userAgent string from Firefox to LibreWolf and way too much shitty code is confused by it looking like firefox but then not being firefox.
I spoof mine to say chrome; got tired of lying ass websites saying their page doesn’t work in Firefox. First, fix your shit if that’s the case. Second, yeah, it probably does.
Be careful what you wish for, that’s how you end up with Chrome’s weird semi-proprietary Sec-CH-UA headers
… and they’ve changed it back.
Really? If so they haven’t pushed it to the main Debian repository
Changed in 138.0-2, reverted in 138.0.1-1 which I got from repo.librewolf.net.
According to @librewolf@chaos.social it’s still a problem in the current build if you have resist fingerprinting turned off.
You can’t stop sending it. That triggers bot detection. If you send a fake header, that doesn’t match existing fingerprints of that browser, bot detection.
Browsers have gotten too complicated.
Yep, just got this problem too.
