3 ms·

>> The bots didn't identify as FB (used "spoofed" UAs) That's surprising. What were the spoofed user agents that they used? We've run into this issue also, b

>> The bots didn't identify as FB (used "spoofed" UAs) That's surprising. What were the spoofed user agents that they used? We've run into this issue also, but all Facebook bot activity had user agents that contained the string "facebookexternalhit".

rob-olmos 6y ago
I've seen these these two user-agents from FB IPs, maybe others: Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_2 like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko) Version/7.0 Mobile/11D257 Safari/9537.53 Mozilla/5.0 (iPhone; CPU iPhone OS 13_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Mobile/15E148 Safari/604.1 Which also execute javascript in some modified sandbox or something, causing errors, and executing error handlers. Interesting attempt to analyze the crawler here: https://github.com/aFarkas/lazysizes/issues/520#issuecomment-484527859 https://github.com/aFarkas/lazysizes/issues/520#issuecomment...
- lun4r 6y ago
  Yep, these were the UAs we also saw (amongst others). And also in our case those bots were executing the JS, even hitting our Google Analytics. For some reason GA reported this traffic to come from Peru and Philippines, while an IP lookup showed it belonged to FB registered in the US or Ireland