consider disabling HTTP transport after multiple failed requests
|Reported by:||dd32||Owned by:|
|Component:||HTTP API||Keywords:||2nd-opinion needs-patch|
There has been a number of reports over the lifespan of the cURL HTTP transport failing with an error during upgrades:
WP HTTP Error: name lookup timed out
This is a common error from cURL on badly configured installations (specifically, IIRC it lacks DNS Resolving in cURL, sometimes it just required an extended amount of time to resolve, others, it simply can't resolve)
Like we do with fsockopen() I think it'd be worth disabling the cURL transport for x hours when it hits this particular error condition..
Related threads: http://wordpress.org/support/topic/dashboard-issues-rss-error-wp-http-error-name-lookup-timed-out and http://wordpress.org/support/topic/plugins-update-failure Both old threads, so this may only affect a PHP4 version of cURL.. For tracking purposes, I've finally created this ticket.
Change History (6)
- Type changed from defect (bug) to feature request
- Keywords 2nd-opinion added
- Type changed from feature request to enhancement
- Summary changed from consider disabling the cURL HTTP transport for failed requests to consider disabling HTTP transport after multiple failed requests