WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 11 months ago

#16870 closed enhancement (maybelater)

consider disabling HTTP transport after multiple failed requests

Reported by: dd32 Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.9
Component: HTTP API Keywords: 2nd-opinion needs-patch
Focuses: Cc:

Description

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)

comment:1 hakre3 years ago

  • Type changed from defect (bug) to feature request

Looks like a configuration issue a host and not a defect with wordpress.

Version 0, edited 3 years ago by hakre (next)

comment:2 hakre3 years ago

  • Keywords 2nd-opinion removed

comment:3 nacin3 years ago

  • Keywords 2nd-opinion added
  • Type changed from feature request to enhancement

Restoring dd32's keyword until appropriate feedback is given.

comment:4 dd323 years ago

  • Summary changed from consider disabling the cURL HTTP transport for failed requests to consider disabling HTTP transport after multiple failed requests

Looks like a configuration issue on a host and not a defect with wordpress.

Yes, That is the exact problem. The transports are designed that it uses what is available on the host, If WordPress does not take into account a transport failing, we end up in a situation where Updates Notices do not flow through amongst other things. It's in the best interests of WordPress users to protect ourselves against these issues.

comment:5 SergeyBiryukov3 years ago

  • Keywords needs-patch added

There are some similar threads on local forums too.

comment:6 dd3211 months ago

  • Milestone Future Release deleted
  • Resolution set to maybelater
  • Status changed from new to closed

With a dwindling number of transports, and transports which we can increasingly actually rely upon, this isn't as needed as it was 2 years ago.

Note: See TracTickets for help on using tickets.