[wp-trac] [WordPress Trac] #27722: Don't fire a warning when the WP API timeouts — or do so properly.

[WordPress Trac]

#27722: Don't fire a warning when the WP API timeouts — or do so properly.
-------------------------------+-----------------------------
 Reporter:  Denis-de-Bernardy  |      Owner:
     Type:  defect (bug)       |     Status:  new
 Priority:  normal             |  Milestone:  Awaiting Review
Component:  Upgrade/Install    |    Version:  trunk
 Severity:  normal             |   Keywords:
  Focuses:                     |
-------------------------------+-----------------------------
 At the time of writing, I'm systematically getting the following error
 from within the WP admin area's update core section:

 {{{
 An unexpected error occurred. Something may be wrong with WordPress.org or
 this server's configuration.
 }}}

 Two things bother me:

 1. It only fires when SSL is used.
 2. The raw_response content suggests a connection timeout.

 I think the warning itself is of dubious merit. If we decide to keep it,
 it should be more explicit as to what is going on. And it should always
 fire, regardless of whether SSL is getting used or not…

 A possible exception I'd make is when it's a request timeout — in that
 case WP should silently try again a few minutes later — without a warning
 or notice.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27722>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform