[wp-trac] [WordPress Trac] #18738: Improving cron spawning and other non-blocking HTTP requests

[WordPress Trac]

#18738: Improving cron spawning and other non-blocking HTTP requests
---------------------------------+-----------------------------
 Reporter:  johnbillion          |       Owner:  dd32
     Type:  enhancement          |      Status:  accepted
 Priority:  high                 |   Milestone:  Future Release
Component:  HTTP                 |     Version:
 Severity:  normal               |  Resolution:
 Keywords:  has-patch 3.6-early  |
---------------------------------+-----------------------------

Comment (by nicola.peluchetti):

 Hi, two things.

 1) You should update the documentation of
 {{{
 WP_Http_Fsockopen
 }}}
 because as it's now it's a little bit misleading as it says

 {{{

 /**
  * Send a HTTP request to a URI using fsockopen().
  *
  * Does not support non-blocking mode.
 }}}
 While this is not true.
 2) As of now if cUrl is disabled i can't get the CRON to function even if
 it points to an empty call. This is because i think that the call that
 spawns the cron

 {{{

 wp_remote_post( $cron_url, array( 'timeout' => 0.01, 'blocking' => false,
 'sslverify' =>  apply_filters( 'https_local_ssl_verify', true ) ) );

 }}}


 Always fail if the transport used is WP_Http_Streams, which is the default
 if cUrl is disabled.
 I know i can use ALTERNATIVE_WP_CRON but lot's of user complains ( and i
 can reproduce it on my dev server ) that it blocks the request, and i also
 reproduced that in develop

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/18738#comment:12>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software