module17
commented
1 month ago Hi, since the latest patch (version 1.2.120) of crawler-detect, I've encountered an issue where the Yandex mobile browser is being falsely detected as a bot. This seems to be due to the addition of the HTTP_SEC_CH_UA header in the detection process.
In the Yandex mobile browser, the HTTP_SEC_CH_UA header includes the following string: "Not/A)Brand";v="8", "Chromium";v="126", "Yandex";v="24". The string "Yandex" triggers the bot detection, but this is a legitimate browser, not a bot.
Could this detection rule be adjusted in the next patch, or is there a way to configure it to avoid this false positive?
For these requests could you provide the other HTTP_* headers? Importantly the HTTP_USER_AGENT value.
It looks like this could be addressed already with https://github.com/JayBizzle/Crawler-Detect/pull/542
IlyaZholobov
Hi, since the latest patch (version 1.2.120) of crawler-detect, I've encountered an issue where the Yandex mobile browser is being falsely detected as a bot. This seems to be due to the addition of the HTTP_SEC_CH_UA header in the detection process.
In the Yandex mobile browser, the HTTP_SEC_CH_UA header includes the following string: "Not/A)Brand";v="8", "Chromium";v="126", "Yandex";v="24". The string "Yandex" triggers the bot detection, but this is a legitimate browser, not a bot.
Could this detection rule be adjusted in the next patch, or is there a way to configure it to avoid this false positive?