-
Notifications
You must be signed in to change notification settings - Fork 473
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
Bot not detected - WhatsApp #5463
Comments
Not sure if that should be detected as |
As much as it is triggered by the user, it is still a bit as when a user clicks a link, it has the whatsapp bot still visit the Page and then the user visits it, I guess it just collects meta data for its database. But I would still call it a bot since the initial view it's getting isn't the real user |
Would be nice to add this "bot" |
Indeed it is a bot. When you type (or paste) a URL within a WhatsApp conversation, the WhatsApp server loads the URL and parses the Open Graph meta tags. More specifically, it loads the og:image meta tag, which usually loads a relevant image of the URL. It is common to see two hits, like this:
The first loads the URL as it was typed or pasted in the WhatsApp conversation, the second loads the relevant og:image meta tag, in this case a logo. |
Is there any fix to it yet? |
Any update to this issue? |
👍 Any updates? It's a snippet request and it's straightforward to treat it as a ‘bot’ |
I have now tested this myself and indeed during writing of a URL, whatsapp fetches the page to show the preview. (even before sending the message). But the IP address isn't the one of the Whatsapp servers, but the one of the phone, so the app itself fetches the meta tags.
|
it seems not to be added, why? you could count this as social media traffic.... |
it should be detected as mobile app. |
if i test this with web.whatsapp.com and add a link from the shop, i cant see this request. Maybe the WhatsApp "Bot" is using grabing the source of html/text. I can see the call in my access.log from the webserver. |
This issue should be closed. |
Just to make this issue clear, @liviuconcioiu, why do you think this should be closed? One could argue if the app on the phone should count as a bot, but as it is making automated requests the user doesn't initialize, I think excluding it and detecting it as a bot instead of an app wouldn't be unreasonable. |
if we consider useragent Similar functionality is available in applications If Skype SkypePreview is a bot, then this user agent should also be considered a bot, based on the precedent -
user_agent: Mozilla/5.0 (Windows NT 6.1; WOW64) SkypeUriPreview Preview/0.5
bot:
name: Skype URI Preview
category: Service Agent
url: ""
producer:
name: Skype Communications S.à.r.l.
url: https://www.skype.com |
The bot that is not being detected is:
WhatsApp/2.12.15/i
The text was updated successfully, but these errors were encountered: