Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does the rule: navigator.connection.rtt == 0 possibly cause false positives for some cases like Edge? #8

Open
hsluoyz opened this issue Nov 6, 2020 · 3 comments

Comments

@hsluoyz
Copy link

hsluoyz commented Nov 6, 2020

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!

@admitrievsky
Copy link

Under Android WebView navigator.connection.rtt == 0

@DavidOzan83
Copy link

DavidOzan83 commented Sep 27, 2023

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...

@admitrievsky
Copy link

I'm not the developer of this project, but the rtt check was removed some time ago, if I remember correctly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants