[wp-trac] [WordPress Trac] #31737: Unique identifier for Heartbeat API calls

WordPress Trac noreply at wordpress.org
Wed Jul 6 18:50:48 UTC 2022

#31737: Unique identifier for Heartbeat API calls
 Reporter:  ojrask                   |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:  Awaiting Review
Component:  General                  |     Version:  3.6
 Severity:  minor                    |  Resolution:
 Keywords:  has-patch needs-refresh  |     Focuses:  javascript

Comment (by pbiron):

 I think this could be useful.  I can't speak for any hosting companies,
 but let me relate an experience I had as customer of one.

 A few years ago, a company which I used for a shared hosting plan
 contacted me and threatened to shut my account down because they were
 **sure** my account had been hacked...because of the traffic that was
 being logged.  A little investigation on my part and I was able to point
 out to them that the traffic they were seeing was simply Heartbeat API
 calls (i.e., I'd login to WP and leave that tab open all day :-).

 I changed my behavior so that the Heartbeat API wasn't exercised as
 much...and the company backed off.

 But, if there had been an easy way for them to verify that the traffic
 they were seeing in their logs was indeed the Heartbeat API...it would
 have saved me a few days of headache thinking my account was about to be
 shutdown :-)

Ticket URL: <https://core.trac.wordpress.org/ticket/31737#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list