Reputation: 21850
Our NodeJS + Express web app has a lot of users who use Opera mini, as the proxy browser helps them save data, and because a lot of them use feature phones.
My query is this:
When we try to intercept the request from Opera Mini, the user-agent-string
is Mozilla/5.0 (Linux; U; Android 5.1.1; en-US; ONE A2003 Build/LMY47V) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 OPR/15.0.2125.101257 Mobile Safari/537.36
Opera's documentation says here that
Opera Mini continues to use Presto on the server, and its UA string is unchanged; it contains the string "Opera Mini".
There is an x-requested-with: "com.opera.mini.native"
in the header as well.
My question is, why is the Mozilla
user-agent
string showing up instead of opera-mini
? I tried on Extreme
as well as High
savings modes. The user-agent
is identical.
What am I missing?
Upvotes: 2
Views: 2514
Reputation:
If I access our site using Opera Mini's extreme data saving mode, I get a different UA string from the one I get when I access it in normal mode.
Normal mode:
Mozilla/5.0 (Linux; U; Android 4.1.1; Galaxy Nexus Build/JRO03C) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30 OPR/22.0.2254.113472
Extreme mode:
Opera/9.80 (Android; Opera Mini/22.0.2254/60.271; U; en) Presto/2.12.423 Version/12.16
The only identifier in the first UA string is "OPR".
Upvotes: 2
Reputation: 11245
Opera Mini disable compress mode on Android by default then you use Wi-Fi and render as native mode (default render engine), practically like WebView.
Opera Mini UA contains Opera Mini only in compress mode.
Upvotes: 1