Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

I would like to override the useragent for a specific site.

  • 4 antwurd
  • 2 hawwe dit probleem
  • 11 werjeftes
  • Lêste antwurd fan cfowler

more options

I have the preference general.useragent.site_specific_overrides set to true and I have general.useragent.override.[website].com set to my desired user agent string. However this setting has no effect.

However, I am able to get a global override by changing the preference general.useragent.override

Also no luck with clearing the global preference and leaving only the site specific preference.

Is there something I am missing? These steps work on desktop versions of firefox.

I have the preference general.useragent.site_specific_overrides set to true and I have general.useragent.override.[website].com set to my desired user agent string. However this setting has no effect. However, I am able to get a global override by changing the preference general.useragent.override Also no luck with clearing the global preference and leaving only the site specific preference. Is there something I am missing? These steps work on desktop versions of firefox.

Keazen oplossing

I upgraded to Aurora 22.02a and the issue seems to have been resolved.

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (4)

more options

Hello cfowler, see if the next add-on is useful : UAControl add-on

thank you

more options

This question is about Firefox on a mobile platform, so instructions for a desktop version do not apply.

more options

Yeeees, cor-el you correct, i see the "system details", i missed the "Product Firefox for Android" details ..........! where i had my mind ?

sorry cfowler, cor-el is correct, forget my reply .

thank you

more options

Keazen oplossing

I upgraded to Aurora 22.02a and the issue seems to have been resolved.