Librewolf

239 readers

1 users here now

Overview:

The secure and private firefox fork!

Related:

founded 4 months ago

Browsers should probably just stop sending user-agent header at all, ideally. (fedia.io)

submitted 2 months ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

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.

top 9 comments

sorted by: hot top controversial new old

[–] [email protected] 15 points 2 months ago

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.

[–] [email protected] 7 points 2 months ago

Be careful what you wish for, that's how you end up with Chrome's weird semi-proprietary Sec-CH-UA headers

[–] [email protected] 5 points 2 months ago (1 children)

... and they've changed it back.

[–] Yingwu 1 points 2 months ago (2 children)

Really? If so they haven't pushed it to the main Debian repository

[–] [email protected] 1 points 2 months ago

Changed in 138.0-2, reverted in 138.0.1-1 which I got from repo.librewolf.net.

[–] [email protected] 1 points 2 months ago

According to @[email protected] it's still a problem in the current build if you have resist fingerprinting turned off.

[–] [email protected] 3 points 2 months ago

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.

[–] [email protected] 1 points 2 months ago

Browsers have gotten too complicated.

[–] Yingwu 1 points 2 months ago

Yep, just got this problem too.