For a long time (at least for recent years), we have been getting a significant amount of incoming traffic (~10k per hour, based on our Cloudflare info) where there is "/undefined" appended to the end of the URL. For example, techlicious.com/tip/how-to-update-an-old-iPad/undefined. When we look at the traffic details in Cloudflare, the behavior is very similar to standard traffic in terms of IP addresses (major US ISPs and large businesses), locations, and even time of day trends. There is a wide range of site URLs that we see this behavior with, but it is weighted heavily towards specific URLs, so it, too, appears more like real user traffic than bot traffic (though the most accessed URLs do not perfectly mirror the most popular URLs in our normal traffic).
It is worth noting that this traffic is not picked up by Google Analytics, which makes us suspect it is bot traffic, despite otherwise looking normal.
The issue is that, at some points, the traffic volume is high enough (over 4x our normal visitor volume) that it puts a strain on our server CPU, so we have been blocking URLs with this extension in Cloudflare. But we don't want to block "legitimate" traffic or other activity, if that's what this is. And despite significant research, we have not been able to find an answer for what would be causing this. We've seen a number of references to how /undefined could be caused by javascript errors, but it's not clear how that would be the case for incoming traffic as it hits our Cloudflare frontend. Would appreciate any insights from the hive mind.
Aucun commentaire:
Enregistrer un commentaire