[wp-trac] [WordPress Trac] #62132: Make wordpress.org API connections for updates, plugins and themes configurable to a different location

[WordPress Trac]

#62132: Make wordpress.org API connections for updates, plugins and themes
configurable to a different location
-----------------------------+------------------------------
 Reporter:  jamesking56      |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by desmith):

 To make my biases clear, I'm looking at this from the POV of a hosting
 provider. Making it a constant makes it harder to break - we can define it
 globally, and don't have to worry about individual customers pointing it
 elsewhere, or plugins (malicious or otherwise) overriding our override.
 The current workarounds (both a pre_http_request filter like the one
 earlier in this ticket, and all the things third-parties already do to
 pull plugins from their own places) should still work with little to no
 impact.

 The filter approach is certainly more flexible, with all both good and ill
 that implies. You're probably right in saying it's the better long-term
 approach for WP as a whole. It also is harder to implement, which means I
 may not be the best one to do it as I'm not an overly experienced dev, but
 I'll take a look in the next few days.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62132#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform