Re:6,953 reasons why I still let Google host jQuery for me
by misterbwong on Tuesday September 21, 2010 @05:16PM
(#1714143)
The one reason we don't use Google's CDN for our public website: Some of our business users block sites by domain or IP, so they allow our site but block google's CDN. It's a PITA to get a rule added to a client's security setup.
[ Parent
| on HN ]
Re:6,953 reasons why I still let Google host jQuery for me
by joshuacc on Tuesday September 21, 2010 @05:37PM
(#1714193)
Do you know why they block Google's CDN?
Re:6,953 reasons why I still let Google host jQuery for me
by misterbwong on Tuesday September 21, 2010 @06:58PM
(#1714441)
I don't know their institutional reasoning, but I believe they are on a whitelist based system. They're not so much blocking Google as they are allowing us through.
Re:6,953 reasons why I still let Google host jQuery for me
by Encosia on Wednesday September 22, 2010 @12:03AM
(#1715131)
That's a scenario that the local-fallback technique handles well. The CDN reference will immediately fail for those overly-firewalled users, jQuery will be undefined in the next script block, and the fallback can detect that and inject a script element referencing a local copy instead.