SM 2.53,1 user-agent missing?

[Anonymosity]

I just examined the headers SM 2.53.1 is exchanging with a web server with Live HTTP Headers, and apparently, SeaMonkey is not sending any user-agent. I also checked 3 different sites that will report your user-agent and all say I am using Windows NT 6.1 and Firefox version 0.0. I suppose that must be the default if no user-agent is sent, but what is going on with SeaMonkey?

[mightyglydd]

They know you're a UA spoofer and spoofed you?

[Anonymosity]

No, these are test sites that give information, and I am not spoofing. I am using MacOS, not Windows.
One example is this: http://dev.jeffersonscher.com/jstest.asp
Another is this one: https://chrispederick.com/work/user-age ... ures/test/
Even if I spoof the user-agent with User Agent Switcher, there is no user-agent!

[ElTxolo]

No, these are test sites that give information, and I am not spoofing. I am using MacOS, not Windows.
One example is this: http://dev.jeffersonscher.com/jstest.asp
Another is this one: https://chrispederick.com/work/user-age ... ures/test/
Even if I spoof the user-agent with User Agent Switcher, there is no user-agent!

• Your user agent, looks a little weird:
  

  Code: Select all

  Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:0.0) Gecko/20100101 Firefox/0.0

  And by the way, using GNU/Linux debian testing, and SeaMonkey 2.53.1
  I don't have those problems you describe. As you can see in these images:
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  Cheers !!!

[therube]

Maybe it is in fact an extension that is breaking your UA?
(Or a manually entered override in, about:config.)
Restart in Safe Mode & see if your expected UA is not being seen as expected.

You can also check your UA in, about:support.


(livehttpheaders-0.17.xpi itself does not look to be an issue.)

[Anonymosity]

I already tried safe mode. I get the same strange user-agent, and also with About SeaMonkey. Maybe it is something wrong with the Mac version of SeaMonkey?

[Anonymosity]

I finally found out what was causing the weird user-agent. It is a setting in about:config:
user_pref("privacy.resistFingerprinting", true);
Why would resisting fingerprinting cause a problem with user-agents?

[TPR75]

I finally found out what was causing the weird user-agent. It is a setting in about:config:
user_pref("privacy.resistFingerprinting", true);
Why would resisting fingerprinting cause a problem with user-agents?

Maybe because it was developed for Tor Browser and shouldn't be enabled in SeaMonkey?
https://wiki.archlinux.org/index.php/Firefox/Privacy

[therube]

I finally found out what was causing the weird user-agent. It is a setting in about:config:
user_pref("privacy.resistFingerprinting", true);

Confirmed.

With privacy.resistFingerprinting, Your browser reports a specific, common version number.
Suppose that part of the code is borked in SeaMonkey.

[frg]

There is a reson that some settings are not activated. This probably needs further work.