[wp-trac] [WordPress Trac] #44229: Use CDNs where possible to serve external assets like jQuery

WordPress Trac noreply at wordpress.org
Sat Sep 22 13:35:53 UTC 2018


#44229: Use CDNs where possible to serve external assets like jQuery
-------------------------+------------------------------
 Reporter:  jacklenox    |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by Otto42):

 The main issue with this suggestion, other than the above mentions about
 GDPR-FUD or countries blocking CDNs, is actually quite simple: WordPress
 is used on lots of sites by users without unrestricted internet access.
 Local intranets run WordPress too, and those users with browsers on an
 internal company system may not have outside access, but still need to
 access internal sites. The site should run properly for such cases as
 well.

 Given how easy it is for plugins to adjust the source of a enqueued item,
 and thus that CDN enabler plugins can exist, this seems best left in
 plugin terrority. Tying WordPress core to a specific CDN provider (even if
 it's one we serve up ourselves like s.w.org) doesn't seem to be a good
 strategy. It can break in edge cases like intranets and country blocking,
 and it ties a fairly important piece of the core to some external
 provider, which can break or go down or just change out from underneath
 us.

 So, nice thought, but not a good idea for core.

 -1

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


More information about the wp-trac mailing list