User Agent Problems

Some websites don’t work well if they don’t recognize the user agent. Much has been written about how browser detection is a flawed system, but some websites still do it. For Privacy Browser, this means that if the default user agent of PrivacyBrowser/1.0 is used, some aspects of certain websites won’t work because the web server doesn’t have PrivacyBrowser/1.0 on the list of user agents that it knows can run a specific feature, so the webserver doesn’t even try to do it, even though Privacy Browser is perfectly capable of handling the feature.

So, for example, neweggbusiness.com doesn’t allow the user to log on if the user agent is PrivacyBrowser/1.0http://hss3uro2hsxfogfq.onion/ loads an entirely blank screen if it doesn’t recognize the user agent. Google doesn’t redirect from HTTP to HTTPS if it doesn’t recognize the user agent, and the Google Play Console doesn’t layout correctly.

PrivacyBrowser/1.0

WebView Default

PrivacyBrowser/1.0

WebView Default

Setting a user agent in domain settings that the website recognizes, like WebView Default, resolves the issue.

One Reply to “User Agent Problems”

  1. This is so stupid. I had issues with Nextcloud on the computer before. It didn’t recognize my useragent so it decided to never show any images.

    And once some online store was just blank for me, it didn’t work at all. It turned out to be the useragent as well. And I don’t get it, nobody can’t be that stupid?

Leave a Reply

Your email address will not be published. Required fields are marked *