Using version 0.5.0 on FF 124 for macos, in custom mode. No later version seems available.
There is a growing number of website that check whether the UA string changes between first and later page loads or clicks.
This is partly done in order tell bots (and other wrong-doers) from human users. Once a change is detected, the page may not load, or not load with all services, or log-in is refused. Typical examples of such pages are using cloudflair services in the background.
The obvious solution is using the switch "Use caching to improve performance", turn it on, so that the once selected UA value is maintained as long as the page is in use.
In the last couple of months there are more and more pages where this approach does not work any more. How do I know ?
first the page does not load as expected,
next I check the caching switch is on or set (it always is ),
next I hover the cursor over the UA switcher icon to read the actual value and reload the page.
move the cursor away and back over the icon to check the value has changed.
What I expect ? ... is to see that the UA string hasn't changed (this would indicate it works as expected).
What I do see instead ? ... is that the UA string has changed on pages where the problem occurs.
Seem that either the caching switch does not work as explained on the options page OR that cloudflair and co. have found a way around this. As soon as I disable the add-on on such pages, the pages load correctly, but this exposes my original UA string and helps them track me.
I would appreciate any comment, will happily provide more details, and otherwise hope for a fix.
Using version 0.5.0 on FF 124 for macos, in custom mode. No later version seems available.
There is a growing number of website that check whether the UA string changes between first and later page loads or clicks. This is partly done in order tell bots (and other wrong-doers) from human users. Once a change is detected, the page may not load, or not load with all services, or log-in is refused. Typical examples of such pages are using cloudflair services in the background.
The obvious solution is using the switch "Use caching to improve performance", turn it on, so that the once selected UA value is maintained as long as the page is in use.
In the last couple of months there are more and more pages where this approach does not work any more. How do I know ?
What I expect ? ... is to see that the UA string hasn't changed (this would indicate it works as expected). What I do see instead ? ... is that the UA string has changed on pages where the problem occurs.
Seem that either the caching switch does not work as explained on the options page OR that cloudflair and co. have found a way around this. As soon as I disable the add-on on such pages, the pages load correctly, but this exposes my original UA string and helps them track me.
I would appreciate any comment, will happily provide more details, and otherwise hope for a fix.