[wp-trac] [WordPress Trac] #17490: HTTP API fails with timeout, if POST-Headers are present

WordPress Trac wp-trac at lists.automattic.com
Fri May 20 23:15:08 UTC 2011

#17490: HTTP API fails with timeout, if POST-Headers are present
 Reporter:  simsmaster    |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  HTTP          |     Version:  3.2
 Severity:  normal        |  Resolution:
 Keywords:                |

Comment (by dd32):

 hi simsmaster,
 I'll do some testing on this later in the week, but in the meantime,
 here's a few things I'd like you to try:

 1. Instal my core Control plugin from the plugin repo, Enable the HTTP
 Access module (You'll find it under Tools I believe)
 2. Post the current list of available transports.
 3. Try disabling the current POST handler transport, then try your code
 again, see if it passes.

 The other thing you can try, is setting a higher than normal timeout, and
 see if that helps:

 $post_data['tip'] = 'adfadf';
 $fetch_url = 'http://mantisbt.org/bugs/login.php';
 $response = wp_remote_post($fetch_url, array('body' => $post_data,
 'timeout' => 90));
 fb($response); //FirePHP

 Also, Trunk includes a fair few bug fixes to the HTTP API, so it's
 worthwhile testing there first before delving deep into code.

 Also, If you're using the cURL transport (from step 2 above) can you post
 the curl version from phpinfo()? (Well, all the curl info would be

Ticket URL: <http://core.trac.wordpress.org/ticket/17490#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list