4 ms·

I hate to say it, but the site isn't loading for me.

• ryankirkman 16y ago
  If it doesn't work for you right now, you can go to: http://122.201.100.216/~cdnjs/ http://122.201.100.216/~cdnjs/ For some reason, the main site is taking ages to propagate to some DNS servers. You're probably covered by one of the servers with an (x) here: http://www.whatsmydns.net/#A/cdnjs.com http://www.whatsmydns.net/#A/cdnjs.com This doesn't actually affect the CDN side, which hosts the scripts. EDIT: For example: http://ajax.cdnjs.com/ajax/libs/backbone.js/0.3.3/backbone-min.js http://ajax.cdnjs.com/ajax/libs/backbone.js/0.3.3/backbone-m... http://ajax.cdnjs.com/ajax/libs/underscore.js/1.1.4/underscore-min.js http://ajax.cdnjs.com/ajax/libs/underscore.js/1.1.4/undersco... http://ajax.cdnjs.com/ajax/libs/modernizr/1.6/modernizr-1.6.min.js http://ajax.cdnjs.com/ajax/libs/modernizr/1.6/modernizr-1.6....
  • corin_ 16y ago
    Firefox can't establish a connection to the server at www.cdnjs.com. Regardless of the reason, doesn't inspire much confidence. Additionally, one of your links, http://ajax.cdnjs.com/ajax/libs/backbone.js/0.3.3/backbone-min.js http://ajax.cdnjs.com/ajax/libs/backbone.js/0.3.3/backbone-m... returns an XML "Access Denied" response. Not a great start ;/
    • ryankirkman 16y ago
      EDIT 2: This issue has now been resolved. The reason you couldn't access this file was that read permissions for the user group "Everyone" were removed on this specific file. We'll endeavor to ensure this doesn't happen in the future. ----------- We might have to put that one down to initial technical difficulties. Not sure why you are getting access denied for that particular resource. May have to invalidate that object from CloudFront cache locations. EDIT: We are using Amazon CloudFront to host the scripts.
  • deleted 16y ago
    [deleted]