You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have observed that 2%-3% Edge traffic that has navigator.connection.rtt set to 0. It's much higher than other headless signals. So I wonder if there can possibly be any false positives for the rule: navigator.connection.rtt == 0 on Edge browsers?
Actually I searched around the Internet, but didn't find a strong evidence to prove that navigator.connection.rtt == 0 indicates a headless bot, except here. Any answers would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered:
admitrievsky, is it possible to remove this navigator.connection.rtt == 0 flag from Android WebView ?
Another question - even if you use WebView normally, you'll still get navigator.connection.rtt == 0.
Meaning that many android users are considered as running with headless.
It doesn't sound right...
We have observed that 2%-3% Edge traffic that has
navigator.connection.rtt
set to 0. It's much higher than other headless signals. So I wonder if there can possibly be any false positives for the rule: navigator.connection.rtt == 0 on Edge browsers?Actually I searched around the Internet, but didn't find a strong evidence to prove that navigator.connection.rtt == 0 indicates a headless bot, except here. Any answers would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered: