?wordfence_logHuman=1&hid=

Confirmed.

Ever since yesterday’s update, the level of wordfence-generated URLs containing those URL parameters has increased exponentially.

In previous versions, these would only appear occasionally – with this version 1-2 are being generated on virtually every user interaction!

These URLs are likely a result of WF’s own interaction with the site, but it would be nice if WF self-filtered those out of the Live Feed…. especially now that they outnumber “real” traffic entries in the live feed at least 2 to 1!

Reviewed a few more client sites… while the increase in WF-generated URLs in the live feed is definitely higher than in previous, it’s not 2:1 as I previously noted. That mustve been an anomaly in that section of the feed…

However, it would still be very helpful if WF self-filtered these URLs from the feed, as they are of zero use to Admins looking at the feeds.

Hi @ditad,

The wordfence_logHuman is supposed to load as an ajax request only.

If the URL to it doesn’t work as expected, it can load the site frontpage instead. Then it would count as a separate visit.

Since we have changed wordfence_logHuman to wordfence_lh in our latest release, any site that still tries to load wordfence_logHuman after upgrading the plugin, will be loading the site frontpage instead of the logHuman call, thus generating an entry in the Live Traffic log.

If you have some cache on the site, please try clearing it.

“The wordfence_logHuman is supposed to load as an ajax request only.

If the URL to it doesn’t work as expected, it can load the site frontpage instead. Then it would count as a separate visit.”

Right, but for the times it does show as a “frontpage load”, can WF not self-filter that entry from the live feed so it’s not even seen regardless?
It really is a pointless feed entry either way since it’s WF-generated!

Thanks. But I don’t understand, what do my visitors see?