Allen,

sure it will work - but...

• there might be some firewall rules on the client side that block them (and you have no influence on that, except for intranet sites)
• there might be some WAF rules that block them
• there might be a CSP that blocks them
• etc.

So better check before setting them in production.

To inject these scripts, you might add the line in the skin ascx file (if you need it on every page), or a copy of the skin file that you use only for the pages where you need it. Or you use Will Strohl's Content Injection module. This is a better way than using module headers or footers...

Happy DNNing! Michael

So DNN itself doesn't do anything to block them?

As far as I can remember, DNN has never itself blocked external scripts. But it's a big security concern these days, so the decision to include external scripts must be deliberate, so that they are not blocked by your own web server(s) and/or the client web browser(s). This only means using a CDN in some cases, but others will require implementing configuration-based exceptions, as Michael mentioned.