Ajax.aspnetcdn.com Expired TLS Cert
1–5 of 5 posts
Re: Ajax.aspnetcdn.com Expired TLS Cert
#2such as
Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available.
// Fallback to loading jQuery from a local path if the CDN is unavailable
(window.jQuery || document.write(''));Re: Ajax.aspnetcdn.com Expired TLS Cert
#3The ASPNETCDN site examples all have a fallback so nothing should have broken if you followed their examples. It's interesting they did this given others do not. such as Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available. // Fallback to loading jQuery from a local path if the CDN is unav…
You know who doesn't seem to understand it, and who conveniently also runs aspnetcdn?
Microsoft, because their partner portal completely bugged out because of this and is unusable without adding a security exception
Re: Ajax.aspnetcdn.com Expired TLS Cert
#4The ASPNETCDN site examples all have a fallback so nothing should have broken if you followed their examples. It's interesting they did this given others do not. such as Production applications should not take a hard dependency on CDN assets. Applications should test for the CDN asset referenced, and use a fallback asset when the CDN is not available. // Fallback to loading jQuery from a local path if the CDN is unav…