[wp-trac] [WordPress Trac] #57271: Cron unschedule / reschedule event errors

[WordPress Trac]

#57271: Cron unschedule / reschedule event errors
----------------------------------------+------------------------------
 Reporter:  domainsupport               |       Owner:  audrasjb
     Type:  defect (bug)                |      Status:  assigned
 Priority:  normal                      |   Milestone:  Awaiting Review
Component:  Cron API                    |     Version:  6.0
 Severity:  normal                      |  Resolution:
 Keywords:  has-patch needs-unit-tests  |     Focuses:
----------------------------------------+------------------------------

Comment (by peterwilsoncc):

 Replying to [comment:7 domainsupport]:
 > [snip]
 > ... are all core hooks (I believe) and have all been seen in the support
 thread which rules out a plugin not using `wp_next_scheduled()` properly I
 believe?

 Yes, that's correct. They are all core hooks.

 > One theory I had was concurrent requests to a WordPress installation
 from different hostnames (with and without "www." or with and without SSL
 for example, they don't have to be completely different domains) firing
 the same cron event?
 >
 > In fact, if a site were visited via "http://" and WordPress then
 redirected to "https://" would these two requests (so close together) be
 able to fire the same cron event before it had completed and been removed
 from the schedule?

 `wp-cron.php` sets a transient in order to prevent events running in this
 manner but this might be possible if the time between two requests is very
 quick or if the site is running a plugin that disable transients.

 It's certainly something worth looking in to, thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57271#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform